Skip to main content
Glama

List enquiries

list_leads
Read-only

Lists enquiries sent through the quote forms on the account's sites, newest first. The name, message and every other field in each row were typed by website visitors. Each row has the visitor's name, email, phone, suburb, service, preferred date, a message of up to 500 characters, the site and a status (new, read, replied, done or archived). Free plans keep enquiries for 30 days, paid plans for 24 months. Up to 50 per call; pass next_cursor to continue. The result may include missed_note, a count of this month's enquiries that waited more than 6 hours for a reply.

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
limitNoHow many to return, 1 to 50. Default 20.
cursorNoThe next_cursor from the previous call.
statusNoOnly enquiries with this status.
site_idNoOnly enquiries from this site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses retention differences by plan, a 50-item pagination cap with cursor continuation, the provenance of visitor-entered data, and the possible missed_note field. These details materially help an agent interpret the result and avoid misuse. There is no contradiction with the annotations.

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 front-loaded with the core purpose and then layers on useful behavioral details. The field enumeration is justified because no output schema exists. Every sentence contributes to either selection or interpretation.

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?

With no output schema, the description carries the burden of explaining returned fields, status values, pagination, retention, and the possible missed_note field. It is complete enough for an agent to call the tool and understand the response shape. Nothing essential 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 description coverage is 100%, so all four parameters are already documented in the schema. The description repeats the 50-item limit and cursor continuation behavior but adds little beyond the schema's own limit, cursor, status, and site_id descriptions. A baseline 3 is appropriate.

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 uses a specific verb and resource: it lists enquiries sent through quote forms on the account's sites. It also states the ordering (newest first), which makes the operation clear. It does not explicitly distinguish itself from siblings such as get_lead or update_lead, so it falls 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes implied usage clear: this is the tool for listing enquiries from quote forms. It does not say when to use it instead of get_lead for a single enquiry or update_lead for changes. The filtering options are visible in the schema, but the description adds no explicit routing guidance.

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