Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

facebook_adLibrary_ad

Retrieves details for a Facebook Ad Library ad by Library ID or ads/library URL, including status, dates, page info, creative snapshot, and EU audience data.

Instructions

facebookAdLibrary: Ad Details. GET /v1/facebook/adLibrary/ad. Get one Facebook Ad Library ad by its Library ID or ads/library/?id= URL, active or inactive. Returns adArchiveID, pageName, isActive, startDate, endDate, publisherPlatform and the snapshot (body, cards, images, videos, display_format, link_url, cta_text), with the advertiser's pageInfo and, for ads shown in the EU, aaa_info audience data. An ad no longer in the library is a 404. Ids are strings. 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

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_ad"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoFacebook Ad Id
urlNoFacebook Ad Library URL, e.g. https://www.facebook.com/ads/library/?id=1016451784037642
trimNoSet true for a trimmed response.
cache_max_ageNoUse a cached response this old or newer for 0 credits. If none is available, fetch live at the endpoint’s normal price.
get_transcriptNoNot supported: get_transcript=true returns 400. Use the video URLs in snapshot.videos.
allow_long_transcriptionNoAccepted for compatibility and ignored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well, disclosing return fields, 404 behavior, active/inactive support, cost on success, and free cost for errors, blocked requests, invalid requests, and cache hits. It also clarifies that IDs are strings.

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 description is front-loaded with the core operation and then gives useful return and cost details in compact form. It is somewhat dense, but every part provides relevant information for invoking or interpreting the 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?

For a single-record retrieval tool with no output schema, the description is complete enough: it explains accepted identifiers, return contents, 404 behavior, and cost model. No critical context appears missing.

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 coverage is 100%, so the parameter descriptions already document id, url, trim, cache_max_age, get_transcript, and allow_long_transcription. The description adds mostly the ID/URL distinction and that IDs are strings, but does not add substantial meaning beyond the schema.

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

Purpose5/5

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

The description states a specific verb and resource: get one Facebook Ad Library ad by Library ID or ads/library URL. It also scopes the operation to active or inactive ads, making the retrieval purpose unambiguous.

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

Usage Guidelines4/5

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

It gives clear context for when to use the tool: retrieving a single ad by known ID or URL, whether active or inactive. It does not explicitly route users to search_ads or company_ads for discovery, so it is not fully explicit about 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