What is Rube MCP and why use it for Scrapingant tasks?

Rube MCP is a centralized controller that manages tool discovery, connections, and execution. It helps automate Scrapingant tasks with up-to-date schemas and consistent workflow steps.

Why must I search tools first each time?

Tool schemas change over time. Searching ensures you use the current tool slugs and argument formats, avoiding failures from outdated definitions.

How do I know my Scrapingant connection is ready?

Check the status returned by RUBE_MANAGE_CONNECTIONS; it must show ACTIVE before you execute any tools.

scrapingant-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Scrapingant Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/scrapingant

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["scrapingant"]
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 Scrapingant-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `scrapingant`
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/scrapingant-automation/SKILL.md

View on GitHub

Overview

This skill automates Scrapingant operations using Composio's Rube MCP. It emphasizes always searching for current tool schemas before execution and requires a connected Rube MCP with a Scrapingant toolkit. It streamlines discovery, connection management, and tool execution into repeatable workflows.

How This Skill Works

The workflow first uses RUBE_SEARCH_TOOLS to fetch available Scrapingant tool slugs and input schemas. It then ensures a Scrapingant connection is established and ACTIVE via RUBE_MANAGE_CONNECTIONS. Finally, it executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying memory and a session_id, and relies on the latest schemas retrieved earlier to guarantee correct arguments.

When to Use It

When you need to automate a Scrapingant task and want current tool schemas.
When setting up a new Scrapingant workflow and must verify connection status.
When discovering available tools before building a workflow.
When executing a tool, ensuring memory is included and arguments match the schema.
When reusing a session across multiple tool executions or handling pagination.

Quick Start

Step 1: Add Rube MCP endpoint https://rube.app/mcp as an MCP server in your client.
Step 2: Verify RUBE_SEARCH_TOOLS responds to fetch Scrapingant tool slugs and schemas.
Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkit 'scrapingant', then run RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug and memory.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Check RUBE_MANAGE_CONNECTIONS reports ACTIVE before execution.
Use exact field names and types from the tool's input schema.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call (even if empty).
Reuse sessions within a workflow and handle pagination tokens if present.

Example Use Cases

Discover a Scrapingant tool slug for product scraping and execute with validated args.
Set up a new Scrapingant connection and run a workflow once ACTIVE.
Iterate over paginated results by continuing to fetch with updated tokens.
Bulk run multiple Scrapingant tools in a single session.
Validate tool schemas by calling RUBE_GET_TOOL_SCHEMAS and adjusting inputs.

Frequently Asked Questions

Add this skill to your agents