What is zenserp-automation?

Zenserp automation is a workflow that uses Composio's Zenserp toolkit via Rube MCP to perform Zenserp tasks, starting with tool discovery to ensure current schemas.

Do I need to search tools before running workflows?

Yes. Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs, input schemas, and the recommended execution plan.

How do I ensure a workflow runs smoothly?

Verify the Zenserp connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, use exact field names/types from the search results, and include a memory object in all RUBE_MULTI_EXECUTE_TOOL calls.

zenserp-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Zenserp Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/zenserp

Prerequisites

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

Step 2: Check Connection

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

Overview

Zenserp Automation via Rube MCP orchestrates Zenserp tasks through Composio's Zenserp toolkit. It relies on RUBE_SEARCH_TOOLS to fetch current tool schemas and requires an active Zenserp connection configured with RUBE_MANAGE_CONNECTIONS. This approach ensures you discover available tools and use correct slugs before execution.

How This Skill Works

First, discover tools with RUBE_SEARCH_TOOLS to obtain current tool slugs and schemas. Then verify the Zenserp connection is ACTIVE using RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and a session_id.

When to Use It

When automating Zenserp tasks and you need current schemas before execution
When you must establish or verify a Zenserp connection via Rube MCP
When performing stepwise workflows involving discovery, connection check, and execution
When handling recurring or batch Zenserp tasks that rely on session reuse
When troubleshooting tool changes or pagination by re-fetching tool schemas

Quick Start

Step 1: Verify RUBE_SEARCH_TOOLS responds and Zenserp connection is configured
Step 2: Discover available tools with RUBE_SEARCH_TOOLS for your Zenserp use case
Step 3: Check ACTIVE connection and run your chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch up-to-date tool schemas
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before running tools
Use exact field names and types from the discover results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty)
Reuse session IDs within a workflow and handle pagination tokens

Example Use Cases

Discover tools for a Zenserp keyword rank task and execute a specific slug
Set up Zenserp connection and run a tool that fetches SERP data
Batch multiple Zenserp tasks using bulk ops and shared session
Reuse a session across daily rank checks to avoid re-authenticating
Iteratively fetch tool schemas to adapt to API changes and continue workflow

Frequently Asked Questions

Add this skill to your agents