Do I need API keys to use Toneden automation with Rube MCP?

No external API keys are required. Add the MCP endpoint and authenticate through the Rube MCP workflow; the Toneden connection is managed via RUBE_MANAGE_CONNECTIONS.

How do I ensure tool schemas stay current?

Always call RUBE_SEARCH_TOOLS before executing to fetch the latest tool slugs and input schemas.

What should I include in memory for executions?

Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}), to preserve session state and context.

toneden-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Toneden Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/toneden

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["toneden"]
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 Toneden-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `toneden`
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/toneden-automation/SKILL.mdView on GitHub

Overview

Automates Toneden tasks using Composio's Toneden toolkit via Rube MCP. It emphasizes discovering available tools first, verifying an active Toneden connection, and then running workflows safely. Keeping schemas current minimizes errors and hard-coded slugs.

How This Skill Works

First, ensure Rube MCP is connected and RUBE_SEARCH_TOOLS responds. Then activate the Toneden toolkit with RUBE_MANAGE_CONNECTIONS and confirm the session is ACTIVE. Finally, discover tools with RUBE_SEARCH_TOOLS and execute a discovered tool via RUBE_MULTI_EXECUTE_TOOL using the provided memory and session_id.

When to Use It

Automating repetitive Toneden operations across campaigns
Validating and maintaining an ACTIVE Toneden connection before automation
Fetching current tool schemas to adapt workflows
Running chained Toneden tasks in a single session to preserve context
Planning or executing bulk Toneden tasks using multiple tools in one workflow

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client config and verify RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["toneden"] and ensure the session becomes ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS (use_case: 'Toneden operations') and execute a tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug, memory, and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas
Check connection status is ACTIVE before executing tools
Use exact field names and types from the search results
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and handle pagination if present

Example Use Cases

Automate weekly Toneden campaigns by discovering the right tool slugs and executing the update tool with a saved session
Onboard a new Toneden account by connecting via RUBE_MANAGE_CONNECTIONS and running the setup workflow
Bulk-update creatives across multiple campaigns by executing discovered Toneden tools in a loop
Fetch all Toneden tool schemas to plan future automations and tool coverage
Chain multiple Toneden tasks within one session to update metrics and trigger actions in sequence

Frequently Asked Questions

Add this skill to your agents