Skip to main content
Glama

List Facebook leads

list_facebook_leads
Read-onlyIdempotent

List Facebook Lead Ads leads, newest first, 25 per page (meta.count is the total). Each lead has its status (received = still processing, processed = WhatsApp template sent, contact_only, failed), why it got no message (skip_reason) or failed (error_code), its form, campaign, ad set and ad, its contact, and its qualification (qualification_tier, qualification_score 0-100). Filter by status, tier and date range. Answers to the form are not included. qualification_tier: hot, warm (both count as qualified), cold, spam, needs_review (a person should look), unscored (lead qualification off for the account, the lead was too old, or it could not be scored). Spanish names of the tiers: caliente, tibio, frío, por revisar, spam, sin calificar.

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_facebook_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
tierNo
sinceNoYYYY-MM-DD. Defaults: the last 30 days.
untilNoYYYY-MM-DD. Defaults: the last 30 days.
fieldsNoOptional: return only these fields of each record.
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description's job is to add operational context — and it does: 25 records per page, meta.count as the total, newest-first ordering, and explicit meanings for each status and qualification_tier value. It does not cover rate limits or what happens with an empty result, but the substantive behavioral detail is present.

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?

One dense but front-loaded block: purpose and pagination first, then record contents, then filters, then the enum glossary. Nearly every clause adds actionable information, and the tier glossary at the end is clearly separable rather than interrupting the main flow.

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?

With no output schema, the description must describe the return shape, and it largely does (per-lead fields, status, skip_reason/error_code, qualification, pagination and totals). However, it never explains the 'page' or 'fields' parameters or whether an entry can be missing fields, so a caller cannot fully predict the response for all argument combinations.

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 only 50%, yet the description compensates well by defining every status and tier enum value (including Spanish aliases) and confirming date-range filtering. The 'page' and 'fields' parameters go unmentioned, leaving those two to the schema alone, which keeps it from a 5.

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 Facebook Lead Ads leads') plus ordering ('newest first') and page size, which is well beyond a tautology. It implicitly distinguishes itself from get_facebook_lead by noting that form answers are excluded, but it never names a sibling tool 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?

It says what can be filtered ('Filter by status, tier and date range'), which implies the browsing/segmenting use case, but gives no explicit when-to-use vs. when-to-call-get_facebook_lead guidance and no prerequisites. Usage must be inferred from the described capabilities.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources