Facebook_ads
Server Details
Facebook Ads MCP Pack
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 40.2% over 42 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-facebook_ads
- GitHub Stars
- 0
- Server Listing
- Facebook Ads MCP
TDQS
Scored across 36 tools
There are three near-identical Pipeworx routers (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) that only differ in subtle mode/quality flags, plus heavily overlapping 'about entity X' tools (resolve_entity, entity_profile, compare_entities, recent_changes, validate_claim) and five overlapping polymarket_* tools. An agent will struggle to pick cleanly, and the whole set is bolted onto a server named Facebook_ads with only five unrelated fb_* tools.
Nearly everything is snake_case verb_noun (ask_pipeworx, entity_profile, resolve_entity, polymarket_edges), which is predictable. The only deviation is the fb_ prefix group versus the unprefixed Pipeworx tools, and the unversioned/versioned pair (ask_pipeworx_beta) which is readable.
36 tools is heavy, and the mismatch is severe: the server is named Facebook_ads yet only 5 of 36 tools relate to Facebook ads, while the other 31 are an unrelated general-purpose data gateway surface. The count is not justified by the stated purpose.
For its apparent Facebook-ads domain the surface is read-only — list accounts/campaigns/adsets, get campaign, get insights — with no create, update, pause, or delete operations and no ad-creative or ad-level management, leaving obvious lifecycle gaps. The embedded Pipeworx toolset is broad but disjoint from the server's advertised purpose.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "when-will-bitcoin-hit-150k" - }, - { - "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" - } -]New value: +[ + { + "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination" + }, + { + "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "will-bitcoin-reach-100k-in-july-2026" - }, - { - "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026" - } -]New value: +[ + { + "market": "when-will-bitcoin-hit-150k" + }, + { + "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
Related MCP Connectors
Related MCP Servers
- AlicenseAqualityBmaintenanceMeta (Facebook/Instagram) Ads MCP server for ad performance reporting, audience analysis, and competitor ad research.41MIT
- AlicenseNot gradedqualityCmaintenanceMCP server acting as an interface to the Facebook Ads, enabling programmatic access to Facebook Ads data and management features.366MIT
- AlicenseBqualityAmaintenanceMCP server for Meta Marketing API v25.0 — 123 tools for Facebook & Instagram ad campaign management100217 npm79MIT
- AlicenseBqualityAmaintenanceEnables MCP clients to read and analyze Facebook (Meta) Ads marketing data, including campaigns, ad sets, ads, insights, and 190 metrics, with optional write tools that preview changes before applying.34255 npmApache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.