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

Rube MCP is the Composio MCP server used to discover and execute Remarkety tools. You must configure it, call RUBE_SEARCH_TOOLS for schemas, manage connections with RUBE_MANAGE_CONNECTIONS, and execute tools with RUBE_MULTI_EXECUTE_TOOL.

Do I always need to search for tool schemas before executing a workflow?

Yes—tool schemas can change. Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and required arguments; do not hardcode values.

What should I do if tool schemas change mid-workflow?

Re-run discovery with RUBE_SEARCH_TOOLS, re-validate the connection status, and adjust the execution parameters (tool_slug, arguments) accordingly. Maintain memory and session handling as required.

remarkety-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Remarkety Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/remarkety

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Remarkety operations through Composio's Remarkety toolkit via Rube MCP. Start by discovering current tool schemas with RUBE_SEARCH_TOOLS to avoid hardcoding slugs. Ensure an ACTIVE Remarkety connection and follow setup steps before running any workflows.

How This Skill Works

Technically, you first discover available tools using RUBE_SEARCH_TOOLS, then verify the Remarkety connection with RUBE_MANAGE_CONNECTIONS, and finally execute a tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug, arguments, memory, and a session_id. This workflow emphasizes using up-to-date schemas and maintaining proper session/state management.

When to Use It

Starting a new Remarkety automation by discovering current tool schemas.
Running recurring Remarkety workflows while avoiding hardcoded tool slugs.
Diagnosing tool schema changes or connection status before execution.
Performing bulk Remarkety operations and multi-tool workflows.
Reusing session IDs within a workflow to maintain continuity.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint.
Step 2: Verify RUBE_SEARCH_TOOLS responds and shows available Remarkety tools.
Step 3: Run the core workflow: discover tools with RUBE_SEARCH_TOOLS, ensure ACTIVE connection with RUBE_MANAGE_CONNECTIONS, then RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, memory, and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing.
Use exact field names and types from the search results.
Include memory (even empty) in RUBE_MULTI_EXECUTE_TOOL.
Reuse session IDs within a workflow and handle pagination tokens.

Example Use Cases

Discover a tool for a customer re-engagement campaign and execute with proper memory.
Connect to Remarkety via Rube MCP and run a segmentation tool.
Bulk-update multiple campaigns by using RUBE_MULTI_EXECUTE_TOOL in sequence.
Test a new workflow in a sandbox session before production deployment.
Paginate through large tool results and complete automation step-by-step.

Frequently Asked Questions

Add this skill to your agents