Skip to main content
Glama
Sign In

X Ads MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Server Details

Hosted X 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/x-ads-mcp-server
GitHub Stars
0
Server Listing
X Ads MCP Server
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 4 tools

Disambiguation3/5

execute_action and query_data are both labeled 'Step 3 (FINAL)' and share nearly identical required preambles, so an agent may struggle to choose between executing an action versus querying data. query_contexts also overlaps by listing available actions and action details, though its helper role is somewhat clearer.

Naming Consistency4/5

Three tools follow a verb_noun snake_case pattern (execute_action, query_contexts, query_data). prompts_menu deviates as noun_noun, but the overall convention is still readable and mostly consistent.

Tool Count4/5

Four tools is compact and each supports a phase of the workflow. The heavy multiplexing inside query_contexts makes the surface feel slightly thin, but the count fits the server's focused purpose.

Completeness4/5

The set covers context discovery, prompt browsing, execution, and data querying, which are the core phases of the stated workflow. No obvious dead end exists, though lifecycle operations depend entirely on execute_action's dynamic action catalog.

Available Tools

4 tools
execute_actionX Ads Execute ActionA
Destructive
Inspect

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

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, 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_menuX Ads PromptsA
Read-only
Inspect

Browse the X 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_contextsX Ads Setup HelperA
Read-only
Inspect

Helper for planning InsightfulPipe X Ads data queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, 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_dataX Ads Data QueryA
Read-only
Inspect

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

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, 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

    • telegram-ads-mcp

      Free-cat
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that lets AI agents read and manage Telegram Ads campaigns, including listing accounts and ads, reading stats and budgets, and creating/updating ads, CPM, status, and budget by driving the real ads.telegram.org web UI through Playwright with a reused cookie-based login session.
      11
      1
      MIT
    • Opus Growth MCP Connector

      Opus Growth MCP Connectorofficial

      opusgrowth
      A
      license
      Not graded
      quality
      B
      maintenance
      A hosted MCP server that enables managing Google Ads, Microsoft Advertising, TikTok Ads, LinkedIn Ads, and other Google services from ChatGPT, Claude, or any MCP client using natural language, with no code or API keys required.
      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