Meta Ad Library Spend MCP Demo by AdSpendSpy

Find a tracked advertiser

search_tracked_brands

Read-onlyIdempotent

Public demo: Alex Hormozi only (page_id 116482854782233). Ad listings/details expose only approved public creatives; statistics describe this advertiser only. Search your tracked advertisers by name, Meta page ID, or stored Facebook URL. Searches existing local data only; does not resolve vanity URLs through paid providers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "search_tracked_brands"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, openWorldHint=false), and the description adds substantial domain context beyond them: the demo data is limited to one advertiser, listings expose only approved public creatives, statistics describe that advertiser alone, and lookups never hit paid resolution providers. That is exactly the kind of scoping an agent needs before calling.

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?

Three tight sentences with no filler; every clause carries information. The demo caveat is front-loaded, which is defensible for a public sandbox but slightly delays the core verb-resource statement.

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 one-parameter search tool with no output schema, the description covers data scope and result limits adequately. Minor omissions remain: pagination/result-count behavior and match semantics are not mentioned.

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?

The single parameter q has no schema description (0% coverage), so the description must carry it: it explains that q can be a name, a Meta page ID, or a stored Facebook URL. It does not state matching behavior (exact vs substring) or what happens on no match, leaving a small gap.

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 (search) and resource (tracked advertisers) and enumerates the three lookup keys: name, Meta page ID, or stored Facebook URL. This clearly separates it from the sibling list_tracked_brands, which enumerates rather than searches.

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?

Gives an explicit negative constraint ('searches existing local data only; does not resolve vanity URLs through paid providers') and scopes the result set to the public demo advertiser. It stops short of naming sibling alternatives such as list_tracked_brands for when a search term is not available.

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?