Meta Ad Library Spend MCP by AdSpendSpy

Find similar advertisers

find_similar_advertisers

Read-onlyIdempotent

List up to six tracked advertisers similar to a brand (same Facebook page category or niche), each with category, active ads where known, estimated 30-day spend range and one top ad. No sign-in needed. Pass page_id when known, otherwise the exact brand name.

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

Input Schema

Name	Required	Description
`brand`	No	Exact brand or advertiser name as the user wrote it, e.g. "Gymshark". Used only when no page_id is given; never matched to a differently named brand.
`limit`	No
`page_id`	No	Numeric Meta page ID of the advertiser, as returned in earlier results. Preferred when known.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

changedInput schema / properties / page_id / description

Previous value: -"Numeric page_id from search_advertisers, find_similar_advertisers, compare_advertisers or a candidate list. Preferred when known."New value: +"Numeric Meta page ID of the advertiser, as returned in earlier results. Preferred when known."

First observedOct 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only/safe/open-world, so credit goes to the added context: results are capped at six, each carries category, active-ad counts where known, a 30-day spend estimate and one top ad, and no sign-in is required. It also implicitly scopes matching to tracked advertisers, which the annotations do not convey.

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?

Two dense sentences, front-loaded with the resource and result shape, then the invocation rule. No filler or restatement of the title.

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 correctly carries the return shape (fields per advertiser, max six results). All three parameters are covered directly or indirectly, and the only small gap is not naming limit explicitly.

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?

At 67% schema coverage, the description usefully adds the precedence rule between page_id and brand that the schema only implies. 'Up to six' explains the limit parameter's ceiling, though the limit parameter itself is never named.

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

Purpose4/5

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

States a specific verb and resource ('List up to six tracked advertisers similar to a brand') plus the matching basis (same Facebook page category or niche) and the per-result fields. An agent can distinguish it from generic siblings like search_advertisers by the 'similar to' framing, though no sibling is named explicitly.

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?

Provides the key invocation rule — 'Pass page_id when known, otherwise the exact brand name' — which is genuine usage guidance. It does not say when to prefer this over search_advertisers or search_tracked_brands, nor any when-not conditions, so context is implied rather than stated.

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 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?