serpdog-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/serpdog-automation --openclawSerpdog Automation via Rube MCP
Automate Serpdog operations through Composio's Serpdog toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/serpdog
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Serpdog connection via
RUBE_MANAGE_CONNECTIONSwith toolkitserpdog - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitserpdog - 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: "Serpdog 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 Serpdog task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["serpdog"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Serpdog-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit serpdog |
| 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/serpdog-automation/SKILL.mdView on GitHub Overview
Serpdog Automation via Rube MCP lets you orchestrate Serpdog operations using Composio's Serpdog toolkit. It requires an active Rube MCP connection and a live Serpdog connection, and emphasizes discovering current tool schemas before execution to avoid stale slugs.
How This Skill Works
Start by verifying RUBE_SEARCH_TOOLS responds, then connect to Serpdog with RUBE_MANAGE_CONNECTIONS using the serpdog toolkit. Discover available tools, select a tool slug and provide schema-compliant arguments, and execute via RUBE_MULTI_EXECUTE_TOOL with a memory object and a session_id.
When to Use It
- When starting a new Serpdog workflow and you need up-to-date tool schemas.
- When automating a sequence of Serpdog tasks within a single session.
- When you must verify the Serpdog connection is ACTIVE before execution.
- When performing bulk or batch Serpdog operations.
- When you need to handle changing tool schemas or pagination without hardcoding slugs.
Quick Start
- Step 1: Configure Rube MCP by adding https://rube.app/mcp as an MCP server in your client.
- Step 2: Run RUBE_SEARCH_TOOLS to fetch current Serpdog tool schemas.
- Step 3: Manage the Serpdog connection with RUBE_MANAGE_CONNECTIONS (toolkit: serpdog) and then execute a tool with RUBE_MULTI_EXECUTE_TOOL using a memory object and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution.
- Use exact field names and types from search results.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and generate new IDs for new workflows.
Example Use Cases
- Discover a Serpdog task, obtain the tool slug from RUBE_SEARCH_TOOLS, supply schema-compliant args, and run with RUBE_MULTI_EXECUTE_TOOL.
- Automate a sequence of Serpdog operations in a single session by reusing a session_id across multiple tool executions.
- Check that the Serpdog connection is ACTIVE after RUBE_MANAGE_CONNECTIONS before executing any tools.
- Perform bulk Serpdog tasks using RUBE_REMOTE_WORKBENCH and run_composio_tool for batch processing.
- Handle pagination by continuing to fetch tool schemas until all pages are retrieved, then execute with complete inputs.
