Skip to main content
Glama

Leads read

leads_read
Read-onlyIdempotent

Counts the leads of a Meta campaign, ad set, ad or instant form (scope and its Meta id) from since to until, in the ad account's days: the total, by day, by form, by ad set and by ad, with the address of the Leads tab. The leads themselves (when each came, every answer, the form and the ad) are a CSV at file, signed for the connected person, valid for one hour and opened once signed in to Adrails. The result holds no name, email, phone or answer: Meta is asked for each lead's id, time and ad alone. A connection without the leads permissions, or a Page the business connection did not grant, returns the Leads tab's sentence saying what grants it.

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": {
      "input": "<input>"
    },
    "name": "leads_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
accountIdsNoOptional account selection; can only narrow this workspace's access.
userStatementNoRequired for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence.
idempotencyKeyNoRequired for mutations. Reuse the same key only when retrying the exact same call; a completed outcome is applied once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses that raw lead data is delivered as a signed, one-hour-lived CSV requiring an Adrails sign-in, that the aggregate result deliberately excludes name/email/phone/answers, and what failure looks like when permissions or Page grants are missing. The only softness is the vague phrasing of the failure sentence ('returns the Leads tab's sentence saying what grants it').

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?

Front-loaded with the verb, scope and output breakdown, and most sentences carry real information. The final sentence is convoluted and the CSV/'file' passage is longer than needed given that 'file' appears nowhere in the input schema.

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 does the necessary work of enumerating what is returned (total, by day, by form, by ad set, by ad, plus the Leads tab address) and describing the out-of-band CSV. It leaves the relationship between accountId and accountIds unexplained and never resolves where 'file' comes from, which is a meaningful gap for a nested-object input.

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?

Adds real meaning beyond the 75%-covered schema: the four 'scope' values are spelled out in prose, 'id' is framed as the Meta id of the chosen entity, and since/until are qualified as 'the ad account's days', which resolves a genuine timezone ambiguity. It never mentions accountId/accountIds or the optional userStatement, and it references a 'file' the schema does not define, so it is not fully complete.

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?

States a specific verb and resource ('Counts the leads') plus the exact scope domain ('a Meta campaign, ad set, ad or instant form') and the aggregation dimensions returned. An agent can distinguish this from siblings like lead_sheet_sync_status or metrics_daily without opening the schema.

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?

Implicitly conveys usage (retrieve lead counts for a Meta entity in a date range) and hints at constraints via the permissions paragraph, but never states when to prefer this tool over alternatives or when-not to use it. The reader must infer routing from the purpose statement alone.

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.