SiteCheck Shop & Social

Ads from Meta's official Ad Library API, by keyword or page

social_facebook_ads_library

Read-only

Ads from Meta's official Ad Library API, by keyword or page IDs and country: ad ID, page, funding byline, creation and delivery dates, creative texts, snapshot URL, platforms, languages and, for political or issue ads, spend and impression ranges; EU reach for EU ads. Covers political/issue ads worldwide and all ads delivered in the EU/UK. Needs the operator's free Ad Library API token. Related tools on this server, for a different need: social_facebook_events when you need Events listed on a Facebook Page's Events tab: event id; social_facebook_followers_following when you need Facebook Page follower counts from Facebook's public Page. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "social_facebook_ads_library"
  }
}

Input Schema

Name	Required	Description
`q`	No	Search words (or use pageIds)
`limit`	No	1 to 50 ads (default 10)
`adType`	No	ALL or POLITICAL_AND_ISSUE_ADS (default). ALL only returns ads for EU/UK countries
`country`	No	Two-letter country the ads reached, e.g. US, DE (ALL for every country)
`pageIds`	No	Up to 10 Facebook page IDs, comma separated
`activeStatus`	No	ACTIVE, INACTIVE or ALL (default ALL)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well past the readOnlyHint/openWorldHint annotations by disclosing the authentication requirement (operator's free Ad Library API token), the metering model ($0.002 USDC per successful call via x402 on Base, Solana or Arc) and that failed calls are not charged. It also discloses the API's coverage limits, which determine what results an agent can expect.

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?

Front-loads what the tool returns, then coverage, then the token requirement, then alternatives with an explicit 'for a different need' framing, then price. The long semicolon-chained field list is dense but each clause carries information; only the sibling descriptions are slightly more verbose than needed.

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?

With an output schema present, the description need not explain return values, and it correctly focuses on coverage, auth, and billing. Nothing critical is missing for a read-only search tool with zero required parameters, though a note on result ordering or pagination limits would complete it.

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 is already documented, and the description's phrase 'by keyword or page IDs and country' only restates the q/pageIds/country split. The adType/coverage sentences add some interpretive context but no syntax or default guidance 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?

States a specific verb and resource - retrieving ads from Meta's official Ad Library API - and enumerates the returned fields (ad ID, page, funding byline, dates, creative texts, snapshot URL, platforms, spend/impression ranges, EU reach). It also names the sibling tools it is not (social_facebook_events, social_facebook_followers_following), so an agent can route without opening schemas.

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?

Explicit coverage rules tell the agent when this applies: political/issue ads worldwide and all ads delivered in the EU/UK, with ALL adType restricted to EU/UK. It also points to two siblings for different needs and names the required API token, though it does not state a case where this tool should be avoided entirely.

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

All SiteCheck Shop & Social tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?