Do I need API keys to use Rube MCP with Campaign Cleaner?

No API keys are required for MCP. Add the MCP server endpoint (e.g., https://rube.app/mcp) and rely on the platform authentication flow.

What happens if tool schemas change?

Always call RUBE_SEARCH_TOOLS first to fetch current schemas and avoid hardcoding; adapt tool_slugs and arguments from the latest results.

Why must memory be included in RUBE_MULTI_EXECUTE_TOOL?

Memory is required to preserve context across tool executions and ensure correct state management within a workflow.

campaign-cleaner-automation

Scanned

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

Files (1)

SKILL.md

3.0 KB

Campaign Cleaner Automation via Rube MCP

Automate Campaign Cleaner operations through Composio's Campaign Cleaner toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/campaign_cleaner

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Campaign Cleaner connection via RUBE_MANAGE_CONNECTIONS with toolkit campaign_cleaner
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 campaign_cleaner
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: "Campaign Cleaner 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 Campaign Cleaner task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["campaign_cleaner"]
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 Campaign Cleaner-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `campaign_cleaner`
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/campaign-cleaner-automation/SKILL.md

View on GitHub

Overview

Automate Campaign Cleaner operations through Composio's Campaign Cleaner toolkit using Rube MCP. It coordinates tool discovery, connection checks, and execution of cleaner tasks, reducing manual setup. Always fetch current tool schemas before running workflows to adapt to changes.

How This Skill Works

The workflow starts by calling RUBE_SEARCH_TOOLS to fetch available Campaign Cleaner tool slugs and input schemas. Next, it uses RUBE_MANAGE_CONNECTIONS to ensure the Campaign Cleaner toolkit is ACTIVE. Finally, it runs RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and proper memory payload, using a session_id for continuity.

When to Use It

You are setting up a new Campaign Cleaner automation and need to discover available tasks dynamically.
You must verify the Campaign Cleaner connection is ACTIVE before executing any tools.
You want to execute one or more discovered tools in a single workflow with a memory context.
Tool schemas may change; you need to re-fetch schemas and adapt without hardcoding slugs.
You prefer reusing a session_id within a workflow for continuity or generate new IDs for new runs.

Quick Start

Step 1: RUBE_SEARCH_TOOLS with use_case set to Campaign Cleaner tasks to discover available tools.
Step 2: RUBE_MANAGE_CONNECTIONS for toolkits: ["campaign_cleaner"] and confirm ACTIVE status.
Step 3: RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, proper arguments, memory: {} , and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas and avoid hardcoding slugs.
Check that RUBE_MANAGE_CONNECTIONS reports an ACTIVE status before execution.
Use exact field names and types from the tool schemas returned by RUBE_SEARCH_TOOLS.
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and generate new ones for separate runs; monitor pagination tokens if present.

Example Use Cases

Discover tools for Campaign Cleaner operations, select a tool_slug from the results, then execute it with RUBE_MULTI_EXECUTE_TOOL and a memory payload.
After establishing an ACTIVE connection via RUBE_MANAGE_CONNECTIONS, run multiple campaign_cleanup tools in sequence within a single session.
If tool schemas update, re-run RUBE_SEARCH_TOOLS to fetch the latest slugs and args before execution.
Perform bulk operations using RUBE_REMOTE_WORKBENCH with run_composio_tool() to apply the same cleanup across campaigns.
Obtain full tool schemas with RUBE_GET_TOOL_SCHEMAS for tools that expose a schemaRef, ensuring compatibility.

Frequently Asked Questions

Add this skill to your agents