Skip to main content
Glama

List captured leads

lead_list
Read-onlyIdempotent

List leads captured from calls and chats, newest first. Filter by date range, capture type, CRM sync status, origin, or a captured field's value. Read only.

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": "lead_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo0-based page number, default 0
sizeNoPage size, default 20
originNoWhere the capture came from
endDateNoISO date, inclusive
fieldKeyNoA captured field name, e.g. "Expected_Check_In_Month"
contactIdNoOnly captures for this contact
startDateNoISO date, inclusive
fieldValueNoThe value that field must have; use with fieldKey
syncStatusNoCRM sync status, e.g. SYNCED, NOT_CONFIGURED, LOCAL_ONLY, FAILED, QUEUED
captureTypeNoCapture type to filter by

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description's "Read only" merely repeats that. The genuinely additive detail is the "newest first" default sort order; nothing is said about result size, rate limits, or what happens when fieldKey/fieldValue are mismatched.

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 tight sentences: the resource and sort order are front-loaded, then the filter dimensions, then the safety note. No redundant phrasing or filler.

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?

For a 10-parameter, all-optional list tool with no output schema, the description covers scope, ordering and filter surface adequately. Minor gaps remain around pagination behavior and result shape, but the schema handles parameter-level detail.

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 every parameter already carries a description including defaults for page/size and the pairing of fieldKey with fieldValue. The description only restates the filter categories rather than adding syntax or interaction details, so it sits at the baseline.

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 concrete verb and resource ("List leads captured from calls and chats") plus the default ordering ("newest first") and the filterable dimensions, so an agent knows exactly what it retrieves. It stops short of distinguishing itself from siblings such as lead_export or contact_timeline, which likely overlap.

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?

The enumeration of filters implies when this tool is the right choice (browsing/segmenting captured leads), but there is no explicit when-not guidance and no named alternative such as lead_export for bulk extraction. Usage is inferable rather than 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.