Skip to main content
Glama
Sign In

Ads Libraries MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Server Details

Hosted Ads Libraries MCP server, with each action switched on or off 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/ads-libraries-mcp-server
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation2/5

execute_action and query_data are nearly indistinguishable: both are labeled as Step 3 (FINAL) of the workflow, both require the same context steps, and one says actions while the other says queries. prompts_menu and query_contexts are distinct, but the core execution tools have unclear boundaries.

Naming Consistency3/5

All names are snake_case, but the pattern is mixed: execute_action, query_contexts, and query_data use verb_noun while prompts_menu uses noun_noun. The inconsistency is readable but not fully predictable.

Tool Count4/5

Four tools is a compact and reasonable surface for this workflow-oriented server. However, the near-duplication between execute_action and query_data means not every tool clearly earns its place.

Completeness3/5

Generic action/query execution plus context lookup likely covers the main Ads Libraries workflow, but prompt handling only supports listing and details, with no create/update/delete operations for custom prompts. This leaves a notable gap in the prompt catalog lifecycle.

Available Tools

4 tools
execute_actionAds Libraries Execute ActionA
Destructive
Inspect

Execute Ads Libraries actions (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

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

  2. request='actions_details' with actions=['xxxxxx'] - Get detailed body structure (replace xxxxxx with actions from available_actions)

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

Inputs: body (required). Returns: object

prompts_menuAds Libraries PromptsA
Read-only
Inspect

Access Ads Libraries prompt catalog with 4 operations:

  1. List Public Prompts:

    • request='menu' - No additional params needed

    • Returns: All public/system prompts for Ads Libraries

  2. List Custom Prompts:

    • request='menu', prompt_type='custom', workspace_id=

    • Returns: All custom prompts for the specified workspace

  3. Get Public Prompt Details:

    • request='prompt_details', prompt_id=

    • Returns: Full text/details of a public prompt

  4. Get Custom Prompt Details:

    • request='prompt_details', prompt_id=, is_custom=True, workspace_id=

    • Returns: Full text/details of a custom prompt

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

query_contextsAds Libraries Setup HelperA
Read-only
Inspect

Helper for planning InsightfulPipe Ads Libraries queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, other source metadata, AND available_actions (all ad library actions you can use).

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

Optional: request='available_actions' – Standalone call to list all available 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 Libraries Data QueryA
Read-only
Inspect

Execute Ads Libraries queries (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

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

  2. request='actions_details' with actions=['xxxxxx'] - Get detailed body structure (replace xxxxxx with actions from available_actions)

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

    • Google Ads Campaign MCP

      clientskatbi
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for managing Google Ads campaigns through the official Google Ads API, covering accounts, campaigns, budgets, keywords, search terms, and keyword ideas. It provides tools for both reading and mutating live ads data, such as pausing campaigns, updating budgets, and adding keywords.
      MIT

    • X Ads by Get MCP Ads

      get-mcp-ads
      A
      license
      B
      quality
      B
      maintenance
      Self-hosted X Ads MCP server with 25 read tools and 19 opt-in, preview-first write tools. Maintained source: get-mcp-ads/x-ads-mcp-server; npm package: @getmcpads/x-ads-mcp-server.
      25
      127 npm
      Apache 2.0

    • meta-ads-mcp

      pralayasimha23
      A
      license
      A
      quality
      D
      maintenance
      MCP server for Meta Ads (Facebook Ads) that provides tools for account discovery, campaign/adset/ad creation, custom audiences, status updates, performance reporting, and A/B testing.
      36
      Business Source 1.1
    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