Meta Ad Library Spend MCP Demo by AdSpendSpy

Rank landing pages by estimated spend

get_top_landingpages_stats

Read-onlyIdempotent

Public demo: Alex Hormozi only (page_id 116482854782233). Ad listings/details expose only approved public creatives; statistics describe this advertiser only. Rank the landing pages of your tracked advertisers by latest cumulative estimated spend in EUR. Ads are grouped by landing URL with ad, advertiser and active-ad counts, the top-spending advertiser and, when one is stored, a screenshot as screenshot_url (site path) and screenshot_full_url (absolute URL). page_id is an exact advertiser filter; q matches part of the landing URL. timeframe filters when ads were last seen, NOT spend accrued during that period. Zero can mean unavailable estimates.

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

Input Schema

Name	Required	Description	Default
`q`	No	Substring of the landing URL.
`limit`	No
`page_id`	No	Meta advertiser page ID, kept as a string.
`project`	No	Only all is available in the public demo.
`timeframe`	No	Last-seen window; never a period-spend calculation.	30d
`active_only`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed world), so the description's added value here is the demo restriction, the return grouping fields, and the caveat that zero can mean an unavailable estimate. It stops short of describing pagination or limit behavior, but the disclosure is well beyond what annotations provide.

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 demo constraint is front-loaded, followed by what is ranked and returned, then parameter semantics. It is dense but every sentence carries distinct information with no filler.

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 no output schema, the description carries the burden of explaining returns and does so well (grouping by landing URL, ad/advertiser/active counts, top-spending advertiser, screenshot fields). Safety behavior is covered by annotations, leaving only minor gaps around result limits.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 67% schema coverage, the description usefully clarifies three key params: page_id is an exact advertiser filter, q matches part of the landing URL, and timeframe filters last-seen windows rather than period spend. limit, active_only and project remain unexplained, but the description adds real meaning over 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 (rank), resource (landing pages), grouping dimension (landing URL) and metric (latest cumulative estimated spend in EUR). It is clearly separable from the sibling get_top_ads_stats, which ranks ads rather than landing pages.

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?

It gives demo scope and filter semantics (page_id exact filter, q substring match) but never explicitly says when to prefer this over get_top_ads_stats or list_brand_ads. Usage is implied rather than routed, so an agent must infer the selection condition.

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

All Meta Ad Library Spend MCP Demo by AdSpendSpy 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?