Skip to main content
Glama

List leads

list_leads
Read-onlyIdempotent

People who left their details in a demo’s lead form or email gate (or a collection’s gate), newest first: email, name, company, phone, which demo, source, country, referrer, time, the answers to the form’s custom fields (answers: key, label, value), the campaign they came from (utm: source, medium, campaign, term, content, and ad click ids) and their intent score (0–100: how engaged their viewing session was; null when not computed). Search by query (email, name or company), filter by demo or by utmSource / utmCampaign (exact values), sort: "intent" for the most engaged first. Paginate with cursor. This is personal data: use it for the user’s request only.

Requires: demos:read, leads:read.

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

Input Schema

NameRequiredDescriptionDefault
sortNo"recent" (default): newest first. "intent": highest intent score first.
limitNo
queryNo
cursorNonextCursor from the previous page.
demoIdNo
utmSourceNoOnly leads whose utm_source is exactly this, e.g. "newsletter".
utmCampaignNoOnly leads whose utm_campaign is exactly this.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "\"recent\" (default): newest first. \"intent\": highest intent score first.",
      +  "enum": [
      +    "recent",
      +    "intent"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / utmCampaign
      Added value: +{
      +  "description": "Only leads whose utm_campaign is exactly this.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • addedInput schema / properties / utmSource
      Added value: +{
      +  "description": "Only leads whose utm_source is exactly this, e.g. \"newsletter\".",
      +  "maxLength": 200,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive safety profile, and the description goes beyond them: it discloses `cursor`-based pagination, the sort modes, the personal-data handling restriction, and the required scopes (demos:read, leads:read). Gaps remain only around page size limits and total-count behavior, which `limit` in the schema partly covers.

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?

One dense but well-ordered paragraph: resource definition and field inventory first, then filtering/sorting, then pagination, then the privacy caveat. Every clause carries information, though the long parenthetical field list is heavy and could be split into shorter sentences.

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?

There is no output schema, so the inline inventory of returned fields (answers, utm fields, intent score with its 0–100 range and null case) is doing necessary work for an agent that needs to interpret results. For a 7-parameter filtered list tool, the definition is nearly complete; only the `limit` default and max go unmentioned.

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?

With 57% schema coverage, the description meaningfully compensates: it explains that `query` searches email, name or company (schema says only 'string'), that utm filters are exact-value matches, and that `sort: "intent"` ranks by engagement. Only `limit` and the precise semantics of `demoId` are left to the schema.

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?

The description states a concrete resource and scope: people who submitted a demo's lead form or email gate, returned newest first, with an enumerated set of fields. That defines the resource far better than the bare name. It does not explicitly distinguish itself from lookalike siblings such as list_captures, so it stops short of a 5.

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 tells the agent how to narrow results (`query` for email/name/company, `utmSource`/`utmCampaign` as exact matches, `sort: "intent"` for most-engaged-first) and how to page with `cursor`. It adds a usage restriction — personal data, use only for the user's request. It never names an alternative tool or a when-not-to-use condition, which keeps it at 4.

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.