Skip to main content
Glama

List a campaign's leads

list_campaign_leads
Read-only

Use this when the user asks who is in a campaign and how each person is doing: where they are in the sequence, whether they opened, clicked, replied or accepted an invitation, the A/B variants they were given and the account that first wrote to them. search matches a name or a company; for the next page, send the page's next cursor with the same search. Free.

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": {
      "campaignId": "<campaignId>"
    },
    "name": "list_campaign_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoThe `pagination.nextCursor` of the page before. Later pages keep the first page's size.
searchNoOnly leads whose name or company contains this text, in any case.
pageSizeNoItems per page.
campaignIdYesThe campaign's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds behavior the annotations don't: that paging requires resending the prior page's nextCursor with the same search, that later pages retain the first page's size, and that the call is 'Free' (no quota cost).

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?

Two sentences plus a one-word cost note, with the trigger and the returned fields front-loaded and pagination behavior trailing. No sentence is filler; the long first sentence is a dense enumeration that earns its length.

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?

For a read-only, four-parameter list tool with a fully documented schema and no output schema, the description covers the trigger, the shape of what comes back, pagination mechanics, matching semantics and cost. Nothing an agent needs 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.

Parameters3/5

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

Schema coverage is 100%, so the baseline is 3; the schema already documents cursor, search, pageSize and campaignId. The description does add one genuinely non-obvious constraint not in the schema — that the same search value must accompany a next-page cursor — but adds no format or matching nuance for campaignId or pageSize.

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 states a specific resource (a campaign's leads) and enumerates exactly what is returned per lead: sequence position, opens/clicks/replies/invitation acceptance, A/B variants, and the originating account. That field list distinguishes it from aggregate siblings like get_campaign_stats and from queue tools far more effectively than a generic 'list leads' phrasing would.

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?

It gives an explicit trigger — 'Use this when the user asks who is in a campaign and how each person is doing' — which is clear context for invocation. It also explains the pagination workflow, but never states when NOT to use it or which sibling to pick for aggregate statistics or queued sends.

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