Facebook Ad Library MCP

EU spend and reach

get_eu_transparency

Read-onlyIdempotent

Look up EU ad transparency data and political or issue ads by brand or advertiser, returning spend, impressions, reach, and demographics from Meta's official Ad Library API.

Instructions

Spend, impressions, reach and demographic breakdown from Meta's official Ad Library API. Covers ads delivered in the EU and political or issue ads anywhere. Returns nothing for an ordinary US commercial ad because that data is not published, which is the correct answer rather than an error. Needs META_ADS_ARCHIVE_TOKEN, which is free.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum ads to return.
`query`	No	Brand or advertiser name to look up.
`country`	No	Two-letter EU country code, e.g. DE, FR, IE. Default DE.
`page_ids`	No	Comma-separated Page IDs, as a more precise alternative to query.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ads`	Yes
`next`	No
`note`	No
`count`	Yes
`country`	Yes
`fields_returned`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.6.1Oct 6, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedOutput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
First observedv0.4.0Sep 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the read-only, idempotent, open-world, non-destructive profile, so the bar is lower. The description still adds real context: the empty-result case is a valid answer rather than an error, and a free token is required. It doesn't discuss rate limits or pagination behavior.

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

Conciseness5/5

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

Three sentences, front-loaded with what is returned and where, followed by the non-obvious empty-result semantics and auth need. No filler or repetition of structured fields.

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?

With an output schema present, return-value explanation is unnecessary, and the description covers scope, the negative-result edge case, and the credential requirement. An agent has everything needed to call it and interpret an empty response.

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 all four parameters are already documented, including the DE default and the page_ids-vs-query distinction. The description adds only indirect meaning via the EU/political scope, so the baseline 3 applies.

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?

States a specific resource set (spend, impressions, reach, demographics) from a named source (Meta's official Ad Library API), which no sibling like search_ads, get_ad, or list_advertisers provides. The EU/political scope clause further pins down the resource it returns.

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?

Explains the crucial when-not case: an ordinary US commercial ad yields nothing and that is the correct answer, not a failure. It also states the auth prerequisite (META_ADS_ARCHIVE_TOKEN). It stops short of routing the agent to a specific sibling for non-EU/non-political ads.

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

Deploy Server