Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

facebook_adLibrary_company_ads

Retrieves a company's Facebook Ad Library ads by page ID or company name, with filters for country, status, dates, language, media type and sort order. Returns paginated results with a cursor.

Instructions

facebookAdLibrary: Company Ads. GET /v1/facebook/adLibrary/company/ads. Provide one of: pageId, companyName. A company's ads from its Ad Library page, with the same filters as ad search. Returns results and a cursor. An empty page costs 0 credits, and an unknown companyName is a 404 at 0 credits. Costs 1 credit when it succeeds. Costs 0 credits when results is empty. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "facebook_adLibrary_company_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoThe cursor from the previous page. Send it with the same filters.
pageIdNoAd Library page id, from /v1/facebook/adLibrary/search/companies. Provide pageId or companyName.
statusNoStatus of the ad. Defaults to ACTIVE.
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.
companyNameNoCompany name, resolved to its Ad Library page (exact name first, else the top match). Provide companyName or pageId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the return shape ('results and a cursor') plus an unusually detailed cost model including 404 and empty-result behavior. However, the cost text is self-contradictory and repetitive ('An empty page costs 0 credits' vs 'Costs 1 credit when it succeeds' vs 'A not-found or empty result is charged only where that operation's published cost says so'), and nothing is said about auth, rate limits, or result fields.

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?

The purpose and endpoint are front-loaded in the first two sentences, which is good structure. The trailing pricing block is bloated and repeats the zero-cost case three times, diluting an otherwise tight definition.

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?

For a ten-parameter read tool with no output schema and no annotations, the description covers purpose, required input choice, return shape (results + cursor) and error/cost behavior. It omits what a result record contains and any pagination limits, but an agent has enough to invoke it correctly.

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 schema already documents all ten parameters including cursor, country, media_type and date bounds. The description only restates the pageId/companyName either-or rule that the schema itself states, adding no new semantics.

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 description names a specific verb and resource ('A company's ads from its Ad Library page') and pins the endpoint, so an agent knows it retrieves ads for one advertiser rather than keyword-searching ads. It stops short of explicitly contrasting itself with facebook_adLibrary_search_ads, only alluding to it via 'the same filters as ad search'.

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?

'Provide one of: pageId, companyName' tells the agent what input is required but not when this tool is preferable to search_ads or search_companies. Usage is only implied by the phrase 'A company's ads from its Ad Library page' – there are no exclusions or named alternatives.

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