Meta Ad Library Spend MCP Demo by AdSpendSpy

List advertiser ads

list_brand_ads

Read-onlyIdempotent

Public demo: Alex Hormozi only (page_id 116482854782233). Ad listings/details expose only approved public creatives; statistics describe this advertiser only. List creative summaries for one tracked advertiser, newest internal ID first, or with sort spend highest latest cumulative estimated spend first (use it for an advertiser's top ads). pagination.next_cursor returns the next page. Each ad carries internal_ad_id (AdSpendSpy ID) and meta_ad_id (the ad on Meta).

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": {
      "page_id": "<page_id>"
    },
    "name": "list_brand_ads"
  }
}

Input Schema

Name	Required	Description	Default
`sort`	No	newest = newest internal ID first; spend = highest estimated spend first.	newest
`limit`	No
`cursor`	No	Opaque pagination.next_cursor returned by the previous page with the same filters.
`page_id`	Yes	Meta advertiser page ID, kept as a string.
`media_type`	No		all
`active_only`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedInput schema / properties / sort

Added value: +{
+  "default": "newest",
+  "description": "newest = newest internal ID first; spend = highest estimated spend first.",
+  "enum": [
+    "newest",
+    "spend"
+  ],
+  "type": "string"
+}

First observedOct 22, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful behavioral context beyond annotations: public-demo restriction to page_id 116482854782233, only approved public creatives being exposed, statistics scoped to this advertiser, and how pagination cursor works.

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 description is front-loaded with the public-demo restriction and then states purpose, sort behavior, pagination, and ID fields. It is information-dense, though the middle sentence is somewhat awkward and partially repeats schema-level sort wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter list tool with no output schema, the description gives reasonable purpose, scope, pagination, and some return identifiers. However, it leaves media_type and active_only undefined and does not fully describe the shape of a creative summary, so clear gaps remain.

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 only 50%, and the description explains sort, cursor, and page_id, but does not compensate for the undocumented limit, media_type, and active_only parameters. It adds some value beyond the schema, especially by explaining that sort=spend is for top ads, but the filter parameters remain underspecified.

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?

The description states a specific verb and resource: 'List creative summaries for one tracked advertiser,' and it clarifies the public-demo scope and default ordering. It implies a distinction from detail/stat tools via 'creative summaries,' but does not explicitly name or contrast with siblings such as get_ad_details or get_top_ads_stats.

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?

It gives clear usage context: list ads for one tracked advertiser, and use sort=spend for an advertiser's top ads. It does not state when not to use this tool or explicitly point to alternative sibling tools for details or statistics.

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?