Do I need API keys to use Rube MCP?

No. You add the RUBE MCP endpoint (https://rube.app/mcp) as an MCP server; no API keys are required.

How do I know when my Listclean connection is ready to run?

Validate by running RUBE_SEARCH_TOOLS to confirm availability, then run RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE before executing tools.

What if tool schemas change and I have existing workflows?

Always re-run RUBE_SEARCH_TOOLS to fetch current tool slugs and schemas; do not hardcode slugs or arguments. Adjust workflows accordingly and re-run with the latest input schema.

listclean-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/listclean-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Listclean Automation via Rube MCP

Automate Listclean operations through Composio's Listclean toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/listclean

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Listclean connection via RUBE_MANAGE_CONNECTIONS with toolkit listclean
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit listclean
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Listclean operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Listclean task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["listclean"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Listclean-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `listclean`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/listclean-automation/SKILL.mdView on GitHub

Overview

Automate Listclean operations through Composio's Listclean toolkit via Rube MCP. It emphasizes discovering current tool schemas first, managing connections, and executing tools with proper session and memory handling.

How This Skill Works

Start by discovering available Listclean tools with RUBE_SEARCH_TOOLS, then ensure an ACTIVE connection using RUBE_MANAGE_CONNECTIONS, and finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and session data. Always pull the latest tool slugs and input schemas from the search results instead of hardcoding values.

When to Use It

You need to automate a Listclean operation without manually selecting tools or writing adapters.
Tool schemas change frequently and you must fetch current slugs and required fields before execution.
You’re integrating Listclean workflows into a larger Composio automation that requires standardized tool discovery and execution.
You must verify the Listclean connection is ACTIVE before running any workflows.
Perform bulk Listclean tasks and require session reuse or consistent session handling across steps.

Quick Start

Step 1: Add the RUBE MCP endpoint (https://rube.app/mcp) as your MCP server and ensure RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'listclean' and verify the connection status is ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then run RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and proper memory.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any workflow to get current tool slugs and schemas.
Check that RUBE_MANAGE_CONNECTIONS shows an ACTIVE status before running tools.
Use exact field names and types from the search results; avoid hardcoding slugs or arguments.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
Reuse session IDs within a workflow when possible; generate a new session only for distinct workflows; watch for pagination tokens and fetch until complete.

Example Use Cases

Discover Listclean tools with RUBE_SEARCH_TOOLS and execute a deduplication task using the latest tool slug.
Establish an ACTIVE Listclean connection, then run a batch cleanup with proper arguments sourced from the current schema.
Automate a Listclean merge/normalize task by first fetching tool schemas, then executing the tool with memory and a reused session ID.
Integrate a Listclean workflow into a larger automation by discovering tools, validating connection, and executing with a single session.
Handle a paginated listclean operation by repeatedly calling RUBE_SEARCH_TOOLS and executing tools with updated schemas.

Frequently Asked Questions

Add this skill to your agents