What is the role of RUBE_SEARCH_TOOLS?

It fetches current Serpapi tool slugs, input schemas, and recommended execution plans.

Why must I verify the connection is ACTIVE?

To ensure authentication and readiness before running any tool calls.

What if tool schemas change?

Always refresh with RUBE_SEARCH_TOOLS to update slugs and input fields; do not rely on hardcoded values.

serpapi-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Serpapi Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/serpapi

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Serpapi operations through Composio's Rube MCP, using live tool schemas to drive workflows. It emphasizes discovering current tool configurations before execution to prevent hardcoded errors. By coordinating discovery, connection management, and execution, it enables scalable Serpapi automation.

How This Skill Works

You first discover available Serpapi tools and their schemas with RUBE_SEARCH_TOOLS. Next, you verify and establish the Serpapi connection via RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, you execute the chosen tools with RUBE_MULTI_EXECUTE_TOOL, supplying the required memory and a session_id, always using the latest discovered schemas.

When to Use It

When you need to automate recurring Serpapi tasks with up-to-date tool schemas
When building a workflow that requires dynamic tool slugs discovered at runtime
When you must validate Serpapi connections before running tools
When performing batch or bulk Serpapi queries while maintaining state across steps
When you want to avoid hardcoding tool configurations and rely on live schemas

Quick Start

Step 1: Verify MCP connection and call RUBE_SEARCH_TOOLS to fetch current tool schemas
Step 2: Use RUBE_MANAGE_CONNECTIONS for the serpapi toolkit and confirm ACTIVE
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, supplying memory and a session_id

Best Practices

Always run RUBE_SEARCH_TOOLS before selecting tools to get current slugs and input fields
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing any tool
Use exact field names and types from the discovered tool schemas; avoid guessing
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({})
Reuse session IDs within a workflow and generate new ones for separate workflows

Example Use Cases

Automating keyword ranking checks across multiple regions using dynamic Serpapi tool schemas
Batch processing SERP results for a marketing campaign with schema-driven inputs
Setting up a fresh Serpapi connection and running initial queries via discovered tools
Orchestrating pagination-aware SERP requests by iterating through schema-guided fields
Scaling Serpapi automation across multiple clients without hardcoding tool slugs

Frequently Asked Questions

Add this skill to your agents