Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Facebook Ad Library ads

facebook_adLibrary_ads_search_get
Read-onlyIdempotent

Search Facebook Ad Library ads by keyword and filters, then return a paginated list for research or monitoring. Use the cursor to continue through additional results.

Instructions

Search Facebook Ad Library ads by keyword and filters. Requires query. Returns a list (use cursor when paginated).

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "facebook_adLibrary_ads_search_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoWhen true, returns a smaller response with fewer fields.
queryYesRequired. Search query text for Facebook Ad Library ads.
adTypeNoOptional filter for all ads or political and issue ads.
cursorNoOpaque pagination cursor from a previous response.
sortByNoOptional sort order for returned ads.
statusNoOptional ad status filter.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
countryNoOptional country code filter. Use ALL to search all countries.
endDateNoOptional end date filter in YYYY-MM-DD format.
languageNoOptional ISO 639-1 language code (two letters, for example EN, ES or FR) to only return ads in that language.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
mediaTypeNoOptional creative media filter.
startDateNoOptional start date filter in YYYY-MM-DD format.
searchTypeNoOptional keyword matching mode for the search query.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered structurally. The description adds only that results are a paginated list with an opaque cursor; it says nothing about result caps, rate limits, or why the response can be trimmed.

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

Conciseness4/5

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

Three short sentences, front-loaded with purpose, then the required parameter, then the return/pagination note. Nothing is padded, though the parenthetical cursor remark is slightly awkward and the whole thing is thin for a 15-parameter tool.

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

Completeness5/5

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

Given 15 parameters all fully described in the schema and no output schema, the description covers what it must: what is searched, that query is mandatory, and that results paginate. The unusual context/llm_model/conversation_id parameters are self-documenting in the schema and need no reiteration here.

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 the baseline of 3 applies. The description's two parameter notes — "Requires `query`" and "use cursor when paginated" — restate what the schema already documents, adding no syntax or format detail beyond it.

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?

The first sentence names a specific verb and resource ("Search Facebook Ad Library ads") and identifies the two axes of the tool: keyword plus filters. This separates it from the ad_get siblings that retrieve one ad, though it never explicitly contrasts with them or with the other-platform ad library searches.

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

Usage Guidelines2/5

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

There is no statement of when to use this search tool versus a single-ad lookup (facebook_adLibrary_ad_get) or a company-scoped listing (facebook_company_ads_list). "By keyword and filters" implies the capability but gives the agent no selection criteria or exclusions.

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