Skip to main content
Glama
Sign In
Meta Ads MCP

Meta Ads MCP

by AbnerZx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

leads_list_from_ad

Retrieve all leads generated by a specific ad. Access and export lead data for analysis or follow-up from Meta Ads.

Instructions

Retrieve all leads generated by a specific ad.

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": {
      "ad_id": "<ad_id>"
    },
    "name": "leads_list_from_ad"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_idYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits beyond the simple retrieval action. It does not mention pagination, rate limits, or whether the returned leads are ordered, and the phrase 'all leads' contradicts the existence of a limit parameter without clarification.

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?

The description is a single, front-loaded sentence that communicates the core purpose without unnecessary words or verbosity.

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

Completeness2/5

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

Although the tool is simple, the description lacks essential context: no usage guidance, no behavioral details, and no explanation of return values (since there is no output schema). The presence of similar sibling tools heightens the need for additional context, which is entirely absent.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not explain the ad_id or limit parameters. The names are somewhat self-explanatory, but the description fails to add any meaning about parameter usage, such as how limit affects results or what format ad_id must take.

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 'Retrieve all leads generated by a specific ad' clearly states the action (retrieve), the resource (leads), and the scope (by a specific ad). It distinguishes from sibling tools like leads_list_from_form and leads_get_lead, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives such as leads_list_from_form or leads_get_lead. It does not mention preconditions, typical use cases, or exclusions, leaving the agent to infer based on the name alone.

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

Deploy Server

Other Tools