What is Moz automation via Rube MCP?

It is automating Moz operations using Composio's Moz toolkit through the Rube MCP connector, with steps to search tool schemas, connect, and execute tools.

Do I need API keys to use Moz automation?

No. You can add the MCP endpoint and connect without API keys, as specified in the setup instructions.

Why must I always call RUBE_SEARCH_TOOLS before executing a tool?

Tool schemas change over time; RUBE_SEARCH_TOOLS ensures you use current slugs and argument names to avoid failures.

moz-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Moz Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/moz

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Moz operations through Composio's Moz toolkit via Rube MCP. This skill emphasizes always searching for current tool schemas before execution and guiding you through connection, discovery, and workflow execution to avoid hardcoding slugs or arguments.

How This Skill Works

The workflow starts by querying Moz tools with RUBE_SEARCH_TOOLS to fetch up-to-date schemas. Next, it establishes or verifies a Moz connection with RUBE_MANAGE_CONNECTIONS, ensuring the toolkit is active. Finally, it runs the chosen tool via RUBE_MULTI_EXECUTE_TOOL, sending the exact schema fields and a memory payload within a session.

When to Use It

You need to automate Moz tasks across multiple runs without manual setup each time
Tool schemas may change and you want to fetch the latest available options instead of hardcoding
You must verify that the Moz connection is ACTIVE before running workflows
You want to discover available Moz tools and their recommended execution plans before choosing a task
You want to reuse session IDs within a workflow and ensure proper memory handling for each tool call

Quick Start

Step 1: Add the MCP endpoint https://rube.app/mcp and ensure RUBE_SEARCH_TOOLS responds
Step 2: Run RUBE_MANAGE_CONNECTIONS with toolkits: [moz] and confirm the connection is ACTIVE
Step 3: Use RUBE_SEARCH_TOOLS to discover Moz tools, then execute a selected tool with RUBE_MULTI_EXECUTE_TOOL including memory: {} and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool schemas
Do not hardcode tool slugs or arguments; use the schemas returned by the tool search
Verify RUBE_MANAGE_CONNECTIONS shows an ACTIVE status before executing tools
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and fetch new ones only for new workflows

Example Use Cases

Automate a Moz link-analysis workflow by discovering tools, validating the connection, and executing the chosen tool with the latest schema
Batch Moz operations across multiple campaigns by iterating over tool slugs returned from RUBE_SEARCH_TOOLS
Reconnect to Moz if the toolkit becomes inactive, guided by the auth flow in RUBE_MANAGE_CONNECTIONS
Fetch the best execution plan from the tool discovery results and run the recommended sequence
Perform bulk Moz tasks using RUBE_REMOTE_WORKBENCH and run_composio_tool with discovered slugs

Frequently Asked Questions

Add this skill to your agents