Skip to main content
Glama
Sign In

Meta Ads MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Server Details

Hosted Meta Ads MCP server for Claude, ChatGPT and Cursor, with each action switched per account.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Insightful-Pipe/facebook-ads-mcp-server
GitHub Stars
0
Server Listing
Facebook Ads MCP Server
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation2/5

execute_action and query_data are described with near-identical boilerplate ('Step 3 (FINAL) of workflow' plus the same query_contexts prerequisite), so an agent has little basis for choosing between them beyond the verbs execute vs query. query_contexts is a clear helper and prompts_menu is distinct, but the two primary workhorses blur together badly.

Naming Consistency4/5

All four names use consistent snake_case, which is predictable. The only deviation is prompts_menu being noun_noun while the other three follow verb_noun, a minor inconsistency.

Tool Count3/5

Four tools is thin for a full Meta Ads surface, but the design deliberately funnels many operations through the two generic dispatchers, so the count is defensible rather than wrong. It still feels under-scoped given campaign/ad set/creative/insights operations all collapse into two opaque entry points.

Completeness3/5

Coverage hinges entirely on the 'actions' discoverable via query_contexts, which is a workable lifecycle mechanism but leaves the surface opaque until runtime. prompts_menu is read-only (browse/fetch, no creation or editing), and there are no explicit tools for common operations like listing campaigns, so agents may hit dead ends without extra discovery steps.

Available Tools

4 tools
execute_actionAds Execute ActionA
Destructive
Inspect

Execute Facebook Ads action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, ad_account_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before executing.

Rely on info from steps 1-2 to construct the action body. Follow the schema exactly.

Inputs: body (required). Returns: object

prompts_menuAds PromptsA
Read-only
Inspect

Browse the ads prompt catalog.

  1. request='menu' – List public/system prompts (optionally pass workspace_id + prompt_type).

  2. request='prompt_details' – Fetch prompt body by prompt_id. Set is_custom=True + workspace_id for workspace prompts.

Inputs: request (required), is_custom, prompt_id, prompt_type, +1 more. Returns: object

query_contextsAds Setup HelperA
Read-only
Inspect

Helper for planning InsightfulPipe ads data queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, ad_account_id, other source metadata, AND available_actions (all tables you can query).

Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, time ranges, and notes for each action.

Optional: request='available_actions' – Standalone call to list all available tables/actions (already included in accounts response).

Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.

Inputs: request (required), actions, brand_id, platform, +1 more. Returns: object

query_dataAds Data QueryA
Read-only
Inspect

Query Facebook Ads data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, ad_account_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before querying.

Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.

Inputs: body (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • Meta Ads MCP Server

      manolocinti
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server to manage Meta Ads campaigns from any machine, deployable on Railway. Supports campaign management via Meta Marketing API through Claude or other MCP clients.
      -

    • meta-ads-mcp

      fujioka0729
      A
      license
      A
      quality
      D
      maintenance
      MCP server to manage Meta Ads (Facebook/Instagram) campaigns, ad sets, insights, and audiences from Claude Code using natural language.
      9
      4 npm
      MIT

    • mlg-meta-mcp

      iammalego
      A
      license
      B
      quality
      D
      maintenance
      MCP server for Meta Ads providing 30 tools for account discovery, campaign management, targeting research, and insights. Designed with LLM-friendly outputs and productivity features like cloning and bulk operations.
      31
      1
      MIT
    Try in Browser
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources