How do I ensure tool schemas are current?

Always call RUBE_SEARCH_TOOLS before executing any tool; tool slugs and arguments can change between runs.

How do I verify the Zenrows connection status?

Use RUBE_MANAGE_CONNECTIONS with the toolkit "zenrows" and confirm the status is ACTIVE before running tools.

What if I need to run multiple tools in a single workflow?

Use RUBE_MULTI_EXECUTE_TOOL with a shared memory object and a consistent session_id; refresh tool schemas periodically with RUBE_SEARCH_TOOLS to stay aligned.

zenrows-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Zenrows Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/zenrows

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Zenrows operations through Composio's Zenrows toolkit via Rube MCP. This approach fetches current tool schemas first, then connects to Zenrows and executes discovered tools. Keeping schemas up-to-date prevents failures from changed tool slugs or parameters.

How This Skill Works

The system first discovers available Zenrows tools using RUBE_SEARCH_TOOLS to obtain up-to-date input schemas. It then verifies the Zenrows connection with RUBE_MANAGE_CONNECTIONS and finally executes the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying exact schema fields, a memory object, and a session_id.

When to Use It

Starting a Zenrows task workflow after fetching the latest tool schemas from RUBE_SEARCH_TOOLS
Verifying or establishing an ACTIVE Zenrows connection before running any tools
Executing a discovered tool by slug with the exact, schema-compliant arguments
Reusing a session_id across multiple Zenrows tools within a single workflow
Handling pagination and continuing tool discovery until all results are retrieved

Quick Start

Step 1: Verify Rube MCP is configured and RUBE_SEARCH_TOOLS is responsive
Step 2: Discover available Zenrows tools with RUBE_SEARCH_TOOLS to get current schemas
Step 3: Establish connection (RUBE_MANAGE_CONNECTIONS) and execute a tool via RUBE_MULTI_EXECUTE_TOOL using memory and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current schemas
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools
Use exact field names and types from the search results; avoid hardcoding
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and regenerate for new runs; watch for pagination

Example Use Cases

Automate product data extraction by discovering Zenrows tools and executing a schema-compliant scraping tool with up-to-date arguments
Collect article headlines across multiple pages by a multi-step Zenrows workflow using a shared session
Validate and scrape e-commerce pricing data with the latest input schemas discovered via RUBE_SEARCH_TOOLS
Migrate a legacy scraper to Rube MCP by replacing hardcoded tool slugs with dynamic discovery
Debug a failed run by re-discovering tool schemas, rechecking connection, and retrying with updated tool slugs

Frequently Asked Questions

Add this skill to your agents