Skip to main content
Glama

Get Facebook marketing overview

get_facebook_marketing_overview
Read-onlyIdempotent

Summarize this account's Facebook Lead Ads leads for a date range: how many arrived (received), how many were sent a WhatsApp template (processed), how many only became a contact (contact_only, with skip_reasons: no_phone, invalid_phone, no_consent, stale = older than 24h, no_routing = follow-up off for the form, template_unavailable), how many failed to be read from Meta, how many replied, how many were qualified (hot or warm) and leads by tier (by_tier), and leads per day. 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": "get_facebook_marketing_overview"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds real domain context beyond that. It decodes the skip_reasons taxonomy (no_phone, invalid_phone, no_consent, stale = older than 24h, no_routing = follow-up off for the form, template_unavailable) and explains why a lead lands in unscored, which an agent could not derive from the annotations. It does not clarify whether the figures are computed live or from synced data, or how fresh they are.

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?

Purpose is front-loaded in the opening clause, and every subsequent clause maps to a returned metric, so there is little pure padding. The trade-off is that it is one very long run-on sentence loaded with nested parentheses, which is harder to scan than a short bulleted breakdown would be. The Spanish tier aliases are the weakest-value portion, though they may help field mapping.

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 carries the burden of explaining return values, and it does so thoroughly -- every named metric in the fields enum is described. The remaining gap is operational: it does not say how these numbers are sourced or how current they are. For a read-only aggregation tool this is close to complete.

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 100% and both date parameters already document the 'YYYY-MM-DD. Defaults: the last 30 days' behavior, and the fields filter is self-documented as a projection list. The description adds no parameter-specific meaning, so the baseline of 3 applies. Its density goes entirely into output semantics rather than input semantics.

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 -- 'Summarize this account's Facebook Lead Ads leads for a date range' -- and enumerates exactly which metrics are aggregated (received, processed, contact_only, replied, qualified, by_tier, by_day). An agent can tell this is an aggregation/reporting tool rather than a record lister. It stops short of naming which sibling to use instead of list_facebook_leads or get_facebook_campaign_insights for related questions, so sibling differentiation is implicit.

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?

There is no when-to-use or when-not-to-use guidance, and no alternatives are named despite many nearby siblings (list_facebook_leads, get_facebook_lead, get_facebook_campaign_insights). The reader must infer from the word 'Summarize' that this is the rollup view rather than the per-lead view. No prerequisites or scope limits are stated.

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