Why must I call RUBE_SEARCH_TOOLS first?

Tool schemas can change. Always fetch current schemas before selecting slugs or arguments to avoid hardcoding.

How do I ensure the Metaads connection is ready?

Use RUBE_MANAGE_CONNECTIONS to check the toolkit status and confirm ACTIVE before executing any tools.

metaads-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Metaads Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/metaads

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Metaads operations through Composio's Metaads toolkit via Rube MCP. It emphasizes discovering current tool schemas, establishing an active Metaads connection, and executing tools in a controlled workflow to keep processes reliable and up-to-date.

How This Skill Works

The skill uses Rube MCP to fetch current Metaads tool schemas with RUBE_SEARCH_TOOLS, then validates the Metaads connection using RUBE_MANAGE_CONNECTIONS. Once a tool slug and its exact schema-compliant arguments are identified, it executes the tool via RUBE_MULTI_EXECUTE_TOOL, including a memory payload and a session_id. For schema freshness, it can optionally pull full schemas with RUBE_GET_TOOL_SCHEMAS before execution.

When to Use It

When you need to automate a recurring Metaads task and require up-to-date tool schemas
When setting up a new Metaads workflow and verifying an ACTIVE connection beforehand
When executing multiple Metaads tools in a single session
When troubleshooting changes to tool slugs or input fields due to schema updates
When performing bulk Metaads operations via remote tooling (RUBE_REMOTE_WORKBENCH) or large-scale campaigns

Quick Start

Step 1: Verify Rube MCP is connected and RUBE_SEARCH_TOOLS responds
Step 2: Manage connections for toolkit metaads and ensure ACTIVE status
Step 3: Discover tools and run a selected tool with RUBE_MULTI_EXECUTE_TOOL using memory and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools
Use the exact field names and types from the retrieved search results
Include a memory object 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

Discover tools for a specific Metaads task, then execute the chosen tool with the appropriate arguments retrieved from the schema
Establish and confirm an ACTIVE Metaads connection before running a campaign optimization tool
Execute multiple Metaads tools in a single session using RUBE_MULTI_EXECUTE_TOOL with memory and session_id
Perform bulk Metaads operations via RUBE_REMOTE_WORKBENCH to update many campaigns in one workflow
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to validate inputs before automation

Frequently Asked Questions

Add this skill to your agents