Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Facebook company ads

facebook_company_ads_list
Read-onlyIdempotent

Lists Facebook Ad Library ads for a company or Page, with optional filters for country, status, media type, dates, and sorting. Use it to inspect a brand's active or historical ad campaigns.

Instructions

List ads a company or Page is running in the Facebook Ad Library. Optional inputs: pageId, companyName, country, status, mediaType and 5 more. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "facebook_company_ads_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque pagination cursor from a previous response.
pageIdNoFacebook page id when you have it instead of a company name.
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 language code filter.
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.
companyNameNoCompany or page name to search when you do not have a page id.
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 readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds only the modest facts that results are paginated by cursor and drawn from the public Ad Library; it says nothing about result volume, limits, or what pagination behavior to expect at the end of the list.

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?

Two short sentences, front-loaded with purpose, followed by input and return hints. The parameter enumeration partly duplicates the schema and the vague 'and 5 more' is filler, but nothing is bloated.

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

Completeness3/5

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

With 13 parameters, 3 enums, and no output schema, the description is thin: it mentions a returned list and cursor but not the shape of returned ads, and it never clarifies the pageId/companyName relationship or the opaque analytics parameters. Adequate to start a call, not complete for a tool of this size.

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 parameter including cursor, pageId, companyName, country, status and mediaType is already documented in the schema. The description merely re-lists five names and hand-waves at '5 more', adding no meaning beyond the structured fields; 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?

States a concrete verb and resource (list ads a company or Page is running) plus the data source (Facebook Ad Library), which is enough for an agent to know what it fetches. It does not distinguish this from siblings like facebook_adLibrary_ads_search_get or facebook_adLibrary_companies_search, so the differentiation gap keeps it at 4.

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 only implied: the tool takes optional identity filters (pageId vs companyName) and a cursor for pagination, suggesting it is the browsing/enumeration entry point for a known advertiser. There is no explicit statement of when to choose this over an ads search tool, and no note that at least one of pageId/companyName is effectively needed.

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