Skip to main content
Glama

List leads

list-leads
Read-only

List leads captured on a domain's lead pages, newest first. Pass since (ISO time) to get only leads created after it. Returns id, created_at, state, page, AI source, score (0-100) and company. Name, email, phone and message are included only for workspace owners on Enterprise Reporting; otherwise they are null and contact_details is 'enterprise_owners_only'. Requires the Lead Pages feature.

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": {
      "domain_id": "<domain_id>"
    },
    "name": "list-leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 25
sinceNoOnly leads created after this ISO time
domain_idYesDomain ID from list-domains

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already establish read-only and non-destructive behavior, and the description adds substantial context beyond them: newest-first ordering, the exact returned fields, privacy gating for contact details, the 'enterprise_owners_only' marker, and the Lead Pages feature requirement. This is rich behavioral disclosure that materially affects how an agent interprets results.

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?

The description is compact and front-loaded: purpose and ordering come first, then filtering, then return values and privacy constraints. Every sentence contributes useful information with no filler.

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 list tool with no output schema, the description covers what is returned, field-level availability, privacy gating, and the feature prerequisite. These are the details an agent needs to call the tool and interpret its output correctly.

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%, so parameter meanings are already documented in the schema. The description restates that 'since' is an ISO time filter and that 'domain_id' comes from list-domains, but adds little about 'limit' or other parameter behavior beyond the schema. Baseline 3 is appropriate.

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 verb and resource ('List leads'), scopes it to a domain's lead pages, and specifies ordering ('newest first'). This is precise enough for an agent to distinguish it from the sibling list-* tools 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?

It gives a prerequisite ('Requires the Lead Pages feature') and explains how to filter with 'since', but it does not name when to use this versus alternatives or describe any when-not conditions. Usage is implied rather than explicitly routed.

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