Skip to main content
Glama
810,787 tools. Updated 2026-11-20 07:47

"A guide to everything about Meta Ads" matching MCP tools:

  • Get the current user's available AI tokens Returns the number of AI tokens available to the authenticated user. These tokens fund EVERY AI feature in SERPmantics — meta, outline, intent, internal-links, EEAT, EEAT competitors, score, AND the AISSistant prompts. The endpoint lives under /aissistant for historical reasons but the balance is shared across all AI features. Do NOT confuse with guide-creation credits (see /api/v1/credits). For a combined view (credits + tokens) prefer /api/v1/credits.
    ConnectorNo auth
  • Create an EMPTY Meta campaign (no ad set or ads). To build a whole campaign with its ad set and ads in one step, use meta_build_campaign instead. Call WITHOUT confirm first to preview exactly what would be created, show that to the human, then call again with confirm: true. Created PAUSED unless activate is explicitly true — an ACTIVE campaign starts spending within minutes. Budget is given in real currency (25.50 means $25.50/day), not cents.
    ConnectorOAuth
  • What to know before going to a venue, from UPFRONT's venue guide: the bag policy and what fans can bring, gates and entry, parking, getting there by transit or rideshare, and food and drink, including what the guide says about gluten-free, vegetarian or vegan, halal and kosher food. Matches questions like "what's the bag policy at MetLife?", "when do doors open at MSG?" or "where do I park for Lambeau?". venue: the venue's name ("MetLife Stadium", "MSG", "Lumen Field, Seattle"). topics: optional; only these parts, at more length: any of "bags", "entry", "parking", "transit", "food". Without it, every part. Covers the 36 stadiums, arenas and amphitheaters UPFRONT has a guide for; for any other venue the answer says so and lists the ones with guides. Each part is the guide's own words ("text", plus the guide's "faq" questions and answers). factsLastChecked is the date UPFRONT last checked the guide's facts; rules can change for a single event, and the venue's own event page has the final word. guideUrl is the guide on UPFRONT. dietary lists what the guide says per diet; dietaryNotMentioned lists diets the guide doesn't cover, which doesn't mean the venue has nothing for them.
    ConnectorNo auth
  • Check whether a Google Ads account is able to spend at all: its account status, whether a billing setup is approved and which payments account and profile it points at, and whether an account budget is pending, cancelled or exhausted. Use this when campaigns look enabled and ads look approved but nothing serves. The Google Ads API exposes no card balance, no billing hold and none of the payment-failure banners the Google Ads UI shows, so an empty blocker list means only that nothing billing-shaped is visible to the API — the result says where to look next. For today's spend and delivery use gads_check_pacing; for per-campaign eligibility use gads_list_campaigns.
    ConnectorOAuth
  • Find body sections in a GOV.UK content item matching a pattern. Returns a list of `{anchor, heading, snippet, match}` hits — small per-section snippets centred on the match — so the LLM can decide which full sections to read via govuk_get_section. Use this when answering content-based questions ("what does this guide say about X?", "find the bit about eligibility") rather than navigating by section number. Pattern is regex; if it doesn't compile, falls back to literal substring.
    ConnectorNo auth
  • Create new guides Create one or more new guides based on provided queries. Each guide targets exactly ONE engine and ONE analysis mode, chosen with the optional `source` field (default `google`). How to request each guide type: 1. Google SERP guide (1 credit per guide): omit `source`, or pass `source: "google"`. Example payload: {"queries": ["best crm"], "lang": "en-us"} 1bis. Google AI Overview guide (1 credit per guide). Two modes, like AI engines: `source: "google_ai_overview"` builds the guide from the TEXT of Google's AI answers (AI Overview, completed with AI Mode answers) ; `source: "google_ai_overview_citations"` builds it from the content of the web SOURCES those answers cite (recommended for GEO). Same language/country parameters as a Google SERP guide, 1 credit per guide in both modes. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "google_ai_overview_citations"} 2. LLM ANSWER guide (4 credits per guide): pass the engine name alone, e.g. `source: "chatgpt"`. The guide is built from the answer text the AI generates for the query. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt"} 3. LLM CITATIONS guide (4 credits per guide) [RECOMMENDED AI mode]: pass the engine name with the `_citations` suffix, e.g. `source: "chatgpt_citations"`. The guide is built from the content of the web pages the AI cites in its answer. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt_citations"} Which AI mode to pick? For GEO (getting a page visible in AI answers), prefer `<engine>_citations`: AI engines send traffic by CITING pages as sources, so the winning move is to look like the pages they cite. The answer-text mode (`<engine>` alone) is mostly useful to analyze how the AI phrases its own answer. When in doubt, pick `<engine>_citations`. The same two modes exist for every AI engine (chatgpt, perplexity, claude, gemini, grok, mistral, deepseek). To optimize the same page for several engines or modes (e.g. Google AND ChatGPT answers AND ChatGPT sources), create one guide per source value on the same query. IMPORTANT, HOW TO READ THE RESPONSE OF THIS ENDPOINT, WHICH SPENDS CREDITS. Queries listed in `guidesFailed` are PROVEN not to have produced a guide and their credit was given back (unless the account has unlimited credits, where nothing was reserved): re-sending them is free and correct. Queries listed in `guidesUnknown` have an UNDECIDABLE outcome and their credit is deliberately KEPT, because the guide was most likely written: DO NOT re-send them, you would pay for the same guide twice. Look them up in `GET /api/v1/guides` after a few minutes instead, and contact support if nothing shows up. Finally, a `200` is NOT a promise that every query produced a guide: compare `guides.length` with the number of queries you sent, never read `success` alone, and never re-send a query just because it is missing from `guides`.
    ConnectorNo auth

Matching MCP Servers

  • F
    license
    A
    quality
    D
    maintenance
    An MCP (Model Context Protocol) server that gives AI agents live, structured ad intelligence across Facebook, Google, and Instagram — data that no base model can produce from training alone. Powered by Apify actors. Works with any MCP-compatible client: Cursor, Claude, etc.
    11
    -
  • F
    license
    A
    quality
    D
    maintenance
    A read-only MCP server that pulls Meta Ads campaign, ad-set, and ad performance data to help users spot problems and adjust them in Ads Manager.
    6
    -

Matching MCP Connectors

  • Spend, campaigns, ad sets and ads on Facebook and Instagram; pause and adjust with approval

  • Meta Ads MCP server: run Facebook and Instagram campaigns, ad sets, ads and reports from AI.

  • Create a new ad group under a campaign. Every ad group belongs to one platform (body.platform, a platform id such as google-ads): only that platform receives it, its ads and its keywords. Leave it out on a campaign that runs on one platform; name it on a campaign that runs on several (400 AD_GROUP_PLATFORM_REQUIRED lists them). It is fixed once created — use copy_ad_group to run the same ads elsewhere. Returns the full updated/created object. Scoped to the active Space — see set_active_space to switch, or pass space_id to override for this one call.
    ConnectorAPI key
  • The store's front door as text: the full menu with prices, how x402 payment works here, the free shelf, and the house promises. Free. Completes when the guide text returns. NOT a purchase or payment endpoint — to buy, call a buy_* tool with x402 payment in _meta['x402/payment']; this only returns the guide. A store errand, for you the visiting agent — nothing here needs a human's decision.
    ConnectorNo auth
  • Stage campaign changes for review. Does NOT execute anything. Each operation: {"platform": "google_ads"|"meta_ads", "level": "campaign"|"ad_set"|"ad" (default campaign; ad_set = Google ad group), "object_id": "<id of that object>", "set": {"daily_budget": <number, MAJOR account-currency units>, "status": "ACTIVE"|"PAUSED"}, "account_id": optional, for multi-account companies}. daily_budget: Meta campaign or ad set, Google campaign only (Google ad group spend is governed by the campaign budget). Ads take status only. Returns proposal_id + a current→new diff preview. Show the preview to the user; call apply_change(proposal_id) only after they confirm. Proposals expire in 1h.
    ConnectorAPI key
  • Get one Durability Curve essay: by default its full public text as markdown, with its title, dates, canonical field, access, length, sections, tools and a link to its claim ledger when it has one. A long essay can be read in parts: part "outline" lists the sections with their opening lines, part "section" returns one, and part "meta" returns everything but the text. For a part-paid essay only the free part is public, and the text says where it stops. The canonical field is the address to cite. These tools retrieve The Durability Curve's public material. They do not certify that any claim is true.
    ConnectorNo auth
  • Render a visual ad carousel widget inline (resource: ui://carousel-mcp-v7). Use this AFTER get_meta_ads, search_meta_ads_by_keyword, get_google_ad_details, search_linkedin_ads, or search_tiktok_ads to show selected ads. Works across ALL FOUR platforms (Meta, Google, LinkedIn, TikTok) and you may mix them in one carousel. Model leads in text — call this when the user benefits from visual evidence of the ads referenced. Call it multiple times in one response, once per point you make — not one carousel for all ads. Pass only the ads that evidence one point: a single creative for one claim, a handful for a pattern. The carousel UI holds 20 ads max — a hard safety cap, not a target; split overflow across another call. Per ad, pass ONLY the identifier ref copied from the prior tool's text output: Meta ads as {ad_id, page_id} (ad_id required, page_id recommended); Google ads as {ad_url}; LinkedIn ads as {linkedin_id}; TikTok ads as {tiktok_id}. Google ads MUST have gone through get_google_ad_details first (it warms the creative cache) — otherwise this call spends credits refetching. LinkedIn ads are warmed by search_linkedin_ads; an uncached one is refetched by id. TikTok ads are warmed by search_tiktok_ads; a stale ref is refetched by tiktok_id (1 credit). Do NOT copy body, headline, media_url, cards or any other field: the server reconstructs the full ad from its own cache, so anything else you pass is discarded.
    ConnectorOAuth
  • Search TikTok's public ads library (EU DSA) by advertiser name. Advertiser names ONLY — this tool cannot search by topic, keyword, product category, industry or ad format ('UGC ads', '3PL warehousing', 'wellness apps' return nothing). For topic research use search_meta_ads_by_keyword or search_competitors, then pass the advertisers they find here. Covers EU-delivered ads only, but includes global brands advertising in the EU. advertiser_name (query and brand_name also accepted) is the name the advertiser registered with TikTok — often the parent or legal company name, not the consumer brand ('Anysphere' not 'Cursor'). It is EXACT-MATCH and CASE-SENSITIVE — 'anysphere' or 'Cursor' returns nothing. So pass a LIST of up to 4 likely variants in ONE call, best guess first — legal/parent company, consumer brand, alternate capitalization (e.g. ['Anysphere', 'Anysphere Inc', 'Cursor']). The server tries them in order and stops at the first with ads (1 credit per name tried, at most 5 credits per call). Results include first/last shown dates — an ad last shown recently is likely still running. No engagement metrics at search level; use get_tiktok_ad_details for landing page and targeting. SHOWING THE ADS — you MUST call show_ad_carousel at least once this turn so the user SEES the TikTok creatives as visual proof, not only reads about them. Pass each TikTok ad as {tiktok_id} copied from this tool's output (the server fills creative, cover and body from cache). Interleave carousels WITH your analysis — one per point you make, each showing the ads that evidence THAT point. Structure strictly as point → its carousel → next point → its carousel; NEVER stack carousels back-to-back or dump all points as a list after the carousels. Be generous: across your carousels, show MOST of the ads this tool returned (up to 20 per carousel) — skip only irrelevant or near-duplicate ads; never render just 2-3 when a dozen were found. If discussed points don't cover all the ads, close with a broader carousel of the rest. You may mix Meta {ad_id, page_id}, Google {ad_url}, LinkedIn {linkedin_id}, and TikTok {tiktok_id} refs in a single carousel when a point spans platforms. Skip it only when there were zero ads.
    ConnectorOAuth
  • Find 10ML's perfume and fragrance guides to read or cite: how-tos (where to spray, finding a signature scent, making perfume last), notes explained, house guides, lists, and alternatives guides that compare famous perfumes with similar ones from other houses. Returns title, type and a link per locale. Use whenever you want a source to cite or a deeper read ('how to layer perfume', 'best oud perfumes', 'Creed Aventus dupes guide'). Not for facts about a perfume (use get_perfume) and not for note definitions (use explain_note).
    ConnectorNo auth
  • Link a GA4 property (properties/<id>) to a Google Ads account, so its key events can be imported into Google Ads as conversions and paid visits join the organic ones. customer_id is the Google Ads account (digits; hyphens are stripped). ads_personalization_enabled shares Analytics audiences and remarketing events with Google Ads — off unless the user asks for it. Read ga4_list_google_ads_links first: a property already linked to this account needs no second link. While linked, Google Ads click and cost data flows into this property and Analytics data flows to that Google Ads account; the link stays until someone removes it in Analytics (Admin, Product links), as this connector cannot unlink. Tools revision: 7a2c68c7.
    Connector
    Destructive
    OAuth
  • Create, list, pause, resume, inspect metrics, or boost organic posts into paid social ad campaigns across LinkedIn Ads, X Ads, Meta (Facebook/Instagram) Ads, and TikTok Spark Ads with 0% Nuntior ad-spend commission. Use this tool when an organic post performs strongly and should be amplified to a targeted B2B or consumer audience with a controlled daily budget. Returns campaign configuration, status, targeting parameters, and real-time spend/conversion snapshots.
    ConnectorNo auth
  • Create, list, pause, resume, inspect metrics, or boost organic posts into paid social ad campaigns across LinkedIn Ads, X Ads, Meta (Facebook/Instagram) Ads, and TikTok Spark Ads with 0% Nuntior ad-spend commission. Use this tool when an organic post performs strongly and should be amplified to a targeted B2B or consumer audience with a controlled daily budget. Returns campaign configuration, status, targeting parameters, and real-time spend/conversion snapshots.
    ConnectorNo auth
  • Purpose: Change a saved monitor without losing what it collected or what the user decided; send only what changes, since everything else stays as saved. When: The user wants a different title, location, company, keyword or field on a saved monitor. Cost: About 160 tokens for the saved monitor.
    Connector
    Destructive
    OAuth
  • Get a link the person opens to connect Meta ads (Facebook and Instagram ad accounts) to their Agency Autopilot account, or to add another Facebook login. One click, then their own Facebook sign-in. The link lasts 30 minutes and works once. It connects nothing by itself, and no password or token is ever entered in the conversation. Use when a tool reports the platform is not connected, or when asked to connect it.
    ConnectorOAuth
  • Neue Meta-Ad anlegen (Bild ODER Video; Website- oder Lead-Anzeige) — Creative + Ad in einem Schritt, Default PAUSED (Aktivierung via meta_update_ad_status). page_id aus meta_list_pages; message = Text über dem Medium, headline/ description = darunter. link: Zielseite — Pflicht, außer bei Lead-Anzeigen (error=link_required). Bild-Ad: image_hash (meta_upload_ad_image) oder direkt image_url. Video-Ad: video_id (meta_upload_ad_video, Status 'ready'; nur Ziffern, sonst invalid_id); image_url/ image_hash dient dann als Thumbnail (sonst Auto-Thumbnail). call_to_action: LEARN_MORE (Default)/SHOP_NOW/SIGN_UP/CONTACT_US/BOOK_NOW/…; bei Lead-Anzeigen Default SIGN_UP (LEAD_GENERATION ist KEIN CTA-Typ) und nur APPLY_NOW/DOWNLOAD/GET_QUOTE/LEARN_MORE/SIGN_UP/SUBSCRIBE erlaubt — andere Typen lehnt das Tool vorab ab (error=invalid_lead_ad_cta). lead_gen_form_id: Instant Form (ID aus meta_list_lead_forms) — macht die Anzeige zur Lead-Anzeige (Bild oder Video): Meta erlaubt dann als link nur den Platzhalter https://fb.me/, der automatisch gesetzt wird; ein anderer link ist error=link_not_allowed_for_lead_ad. Das Adset muss auf LEAD_GENERATION mit promoted_page_id derselben Page laufen (meta_create_adset). Lehnt Meta mit Subcode 1815089 ab, hat kein Page-Admin die Lead-Ads-Nutzungsbedingungen akzeptiert (Antwort enthält hint; Stand vorab in meta_list_pages -> leadgen_tos_accepted). url_tags: UTM-Parameter als eigenes Creative-Feld, z.B. 'utm_source=facebook&utm_medium=paid&utm_campaign={{campaign.name}}'. validate_only: True ist eine reine Parameter-Vorschau OHNE API-Calls — ob Meta die Ad wirklich akzeptiert, zeigt erst der echte Aufruf. Zurücklesen: meta_list_ads zeigt creative.lead_gen_form_id und url_tags. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).
    ConnectorOAuth
  • List the CREATED ads of a project (the ad integrations that already exist, not the catalog of channels you can add — use list_ad_channels for that). Use this to find an existing ad and its ad_id. Ads are product-listing channels (Google Shopping, Meta catalog, Microsoft, price comparison) for the merchant's physical products, not marketplaces: they publish products to the channel and have no order sync. Returns {integrations, returned, total}; each row is {integrationId, projectId, name, channelCode, kind:'ads', definitionCode, status, ready, lastStep, isReady, isConnected, isOverlimit, productMode, orderMode, orderSync}. project_id is OPTIONAL: with it you get that project's ads; WITHOUT it you get ads across ALL your projects (each row carries its projectId). If a call returns project_id_required, pick a project (see list_projects) and pass its project_id. integrationId is what you pass as ad_id to get_ad / ad_status and the other ads tools.
    ConnectorOAuth
  • Create a new ad for a project from one of the channels in list_ad_channels. Use this when the user asks to add an ad channel for their products. Ads are product-listing channels (Google Shopping, Meta catalog, Microsoft, price comparison) for the merchant's physical products, not marketplaces: they publish products to the channel and have no order sync. channel_code is the channelCode from list_ad_channels. Returns {integrationId, action:'create', status, kind:'ads', editUrl, nextStepType, message}. status is 'created' (the ad exists; continue with configure_ad_step starting at nextStepType) or 'prerequisite_not_met' (HTTP 409 — message explains what must be done first, e.g. an offer/primary feed must exist first, or another ad is not included in this Koongo account (the message explains it); nextStepType names the step). multichannel_code links a multichannel definition when the channel offers one. definition_code picks a SPECIFIC definition of the channel when it has more than one — take it from get_ad_channel definitions[].definitionCode; omit it for the channel's default/primary definition. name is an OPTIONAL human-readable label so you can later find this ad by name (names are not unique — set_ad_name can change it later). project_id is OPTIONAL (inferred for a single-project customer; if project_id_required is returned, call list_projects and pass project_id). The returned integrationId is the ad_id for get_ad / configure_ad_step and other ads tools.
    ConnectorOAuth