Meta Ad Library Spend MCP by AdSpendSpy

List spend alerts

list_alerts

Read-onlyIdempotent

List spend alerts for ads of advertisers you actively track, newest first (event ad.spend_alert). Each item carries the alert threshold and the estimated spend when the alert was created. Without since_id or cursor the last 30 days are returned. since_id returns only items with a higher alert_id. Spend is a latest cumulative estimate in EUR; null means unknown. Reading alerts does not mark them as sent. Use page_id or project, not both.

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

Input Schema

Name	Required	Description
`limit`	No
`cursor`	No	Opaque pagination.next_cursor returned by the previous page with the same filters.
`page_id`	No	Meta advertiser page ID, kept as a string.
`project`	No	Public_id of one of your projects. Cannot be combined with page_id.
`since_id`	No	Return only items with a higher id (internal_ad_id for new ads, alert_id for alerts).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses non-obvious side-effect semantics ('reading alerts does not mark them as sent'), the meaning of the spend value (latest cumulative estimate in EUR, null = unknown), and the default time window.

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?

Four tight sentences, purpose-first, then defaults, then value semantics, then the constraint. No filler and each clause carries decision-relevant information.

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

Completeness5/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 still tells the agent what each item contains (threshold and estimated spend at alert time) and how to page. Nothing needed to call it correctly is missing.

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?

Schema coverage is 80%, yet the description still adds value: it clarifies that since_id applies to alert_id here, defines the fallback window when cursor/since_id are absent, and restates the page_id/project incompatibility. The limit parameter goes unmentioned.

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?

Opens with a specific verb and resource plus scope ('List spend alerts for ads of advertisers you actively track') and adds ordering ('newest first') and the underlying event name. It implicitly separates from get_pending_alert_count, but 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete operational rules: default 30-day window when no since_id/cursor, since_id returns only higher alert_ids, and the mutually exclusive 'use page_id or project, not both'. Missing only explicit routing advice versus sibling alert tools.

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?