Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

facebook_adLibrary_search_ads

Search Meta Ad Library ads by keyword and apply country, language, status, media type, ad type, phrase match, sort, and impression-date filters to find matching creatives.

Instructions

facebookAdLibrary: Search. GET /v1/facebook/adLibrary/search/ads. Search the Meta Ad Library by keyword, with the Ad Library's own filters: country, language, status, media type, ad type, exact phrase, sort, and an impressions date range. Returns searchResults (one card per creative group, as the Ad Library shows them: ad_archive_id, page_name, is_active, publisher_platform, collation_count, start/end dates and a snapshot with body text, images, videos, cards and cta_text), searchR Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "facebook_adLibrary_search_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoSet true for a trimmed response.
queryYesKeyword to search for (up to 200 characters)
cursorNoThe cursor from the previous page. Send it with the same filters.
statusNoStatus of the ad. Defaults to ACTIVE.
ad_typeNoSearch for all ads or only political and issue ads
countryNoWhere Facebook showed the ad: one two-letter country code, such as US, or ALL (default). Results can include advertisers from other countries whose ads reached it.
sort_byNoSort by impressions (high to low), or Most Recent (relevancy_monthly_grouped). Defaults to impressions.
end_dateNoOnly ads with impressions on or before this date, YYYY-MM-DD.
languageNoOnly ads in this language: a two-letter code such as EN, ES or FR.
media_typeNoAd media type. Defaults to ALL. MEME means an image with text.
start_dateNoOnly ads with impressions on or after this date, YYYY-MM-DD.
search_typeNokeyword_unordered (default) matches the words in any order; keyword_exact_phrase matches the phrase as written.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does real work: it discloses the credit cost model (1 credit on success, free on errors, blocked, timed-out, invalid requests and cache hits) plus a caveat that empty results are charged per published cost. It does not mention authentication requirements, rate limits, or pagination behavior beyond the cursor field in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is well front-loaded, but the return-value sentence is corrupted mid-stream — 'Returns searchResults (...), searchR Costs 1 credit' — leaving a truncated fragment that reads as an editing artifact. The long parenthetical field list is informative but pushes the cost model, which is decision-relevant, to the very end.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must describe returns, and it does: searchResults cards with ad_archive_id, page_name, is_active, publisher_platform, collation_count, dates, and a snapshot containing body text, images, videos, cards and cta_text. Combined with the cost disclosure this is nearly complete, though the garbled 'searchR' fragment leaves the second return field undefined and pagination is only implied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every one of the 12 parameters is already documented, including defaults like ACTIVE and ALL. The description restates the filter set (country, language, status, media type, ad type, exact phrase, sort, impressions date range) but adds no syntax, format, or interaction detail beyond what the schema provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Search the Meta Ad Library by keyword') and even gives the backing route GET /v1/facebook/adLibrary/search/ads, so the agent knows exactly what operation runs. It enumerates the supported filters, which implicitly separates it from the sibling facebook_adLibrary_company_ads, but never states that distinction explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the filter list — you reach for this when you have a keyword and optional country/language/status constraints. There is no explicit when-to-use versus when-not guidance and no mention of the sibling ad/company tools, so the agent must infer routing from names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools