What is Rube MCP and how does it relate to Idea Scale automation?

Rube MCP is the connector that provides tool discovery and execution. Use RUBE_SEARCH_TOOLS to fetch current schemas and RUBE_MULTI_EXECUTE_TOOL to run the chosen Idea Scale tool.

Why must I always search tools first?

Tool schemas change over time; hardcoding slugs or argument names can break workflows. Always fetch current schemas to ensure compatibility.

What indicates a successful automation run?

An ACTIVE connection status and a successful RUBE_MULTI_EXECUTE_TOOL call with the correct tool slug, required arguments, and a memory field (even if {}), followed by valid results.

idea-scale-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Idea Scale Automation via Rube MCP

Automate Idea Scale operations through Composio's Idea Scale toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/idea_scale

Prerequisites

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

Step 2: Check Connection

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

Overview

Idea Scale Automation via Rube MCP uses Composio's idea_scale toolkit to automate operations. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution and requires an ACTIVE connection via RUBE_MANAGE_CONNECTIONS. This approach keeps workflows robust to schema changes and supports repetitive or bulk tasks.

How This Skill Works

Set up by connecting Rube MCP (no keys required) and verifying RUBE_SEARCH_TOOLS responds. Discover tools for your Idea Scale use case, then check that the connection is ACTIVE. Finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, using the discovered slug and required arguments, including memory (even if empty). Always search tools first to get current schemas.

When to Use It

Automating repetitive Idea Scale submissions or reviews across projects
Fetching the latest tool schemas before starting a new workflow
Verifying the connection is ACTIVE before executing any tools
Performing bulk operations with RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH
Handling multi-step workflows that require fresh tool slugs and session continuity

Quick Start

Step 1: Add the Composio Rube MCP endpoint https://rube.app/mcp as an MCP server and connect the idea_scale toolkit via RUBE_MANAGE_CONNECTIONS
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Idea Scale tool slugs and input schemas for your use case
Step 3: Ensure the connection is ACTIVE, then use RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, proper arguments, memory, and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first; tool schemas change and slugs can be updated
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution
Use exact field names and types from the search results to ensure schema compliance
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and generate new ones for new workflows

Example Use Cases

Automate weekly Idea Scale submissions for multiple teams using updated tool slugs fetched via RUBE_SEARCH_TOOLS
Fetch and adapt to new tool schemas for a new project before running workflows
Bulk update ideas across several campaigns with RUBE_MULTI_EXECUTE_TOOL
Validate that the Idea Scale connection remains ACTIVE before each batch run
Resume a paused workflow by reusing the same session_id and discovered tool slug

Frequently Asked Questions

Add this skill to your agents