Scrape Do Automation via Rube MCP

SkillWeb & browsing

This skill lets your AI scrape web pages through Scrape Do. Once added, your AI can discover the Scrape Do tools available through your connected service and run them to pull web content for you. It handles the Scrape Do steps so you can get page data by simply asking.

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

After adding the skill, ask your AI to look up the available Scrape Do tools first so it works with the latest versions. Then tell it which page to scrape or what task to run.

Then ask your AI: use the Scrape Do Automation via Rube MCP skill

What your AI can do with it

  • Scrape web pages through Scrape Do
  • Discover which Scrape Do tools are available on your connected service
  • Run Scrape Do tools to complete scraping tasks
  • Check the current setup of each tool before using it
  • Automate Scrape Do tasks end to end

What this skill tells your AI

The instructions your AI receives, as published by composio-community/awesome-codex-skills in composio-skills/scrape-do-automation/SKILL.md and read by ahel’s review.

Automate Scrape Do operations through Composio's Scrape Do toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/scrape_do

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Scrape Do connection via RUBE_MANAGE_CONNECTIONS with toolkit scrape_do
  • 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.

  1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  2. Call RUBE_MANAGE_CONNECTIONS with toolkit scrape_do
  3. If connection is not ACTIVE, follow the returned auth link to complete setup
  4. Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Scrape Do 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 Scrape Do task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["scrape_do"]
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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Scrape Do-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit scrape_do
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Powered by Composio

Signals

GitHub stars
17k
Forks
2k
Last commit
Jul 2026

Others that do the same job

Advanced
Item type
skill
Key
scrape-do-automation
Source
github.com/composio-community/awesome-codex-skills