Metaads Automation

What This Skill Does

This skill automates Metaads operations through Composio's Metaads toolkit via Rube MCP. It enables users to manage and optimize their Metaads campaigns and data through automated workflows. This is useful for marketers and advertisers looking to streamline their Metaads processes.

When to Use

• Create new ad campaigns.
• Update existing ad sets.
• Generate reports on ad performance.
• Manage ad budgets Target specific audiences.
• Optimize ad creatives.

Key Features

Automates Metaads tasks via Rube MCPUses Composio's Metaads toolkit Requires an active Metaads connection Discovers available tools using RUBE_SEARCH_TOOLSChecks connection status with RUBE_MANAGE_CONNECTIONSExecutes tools using RUBE_MULTI_EXECUTE_TOOL

Manual Installation

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

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: {}

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

Powered by Composio