NeoMind

Leads

list_leads

Read-only

List the leads your AI team captured (name, contact details, what they want, status), newest first. Filter by status, search text (name, email or phone) or a captured-date range.

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

Name	Required	Description
`q`	No	Search name, email or phone.
`to`	No	Only leads captured before this ISO date, e.g. 2026-10-08.
`from`	No	Only leads captured on or after this ISO date, e.g. 2026-10-01.
`limit`	No	How many leads to return (1–50, default 20).
`offset`	No	How many leads to skip, to fetch the next page (default 0).
`status`	No	Only leads with this status.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing sort order ('newest first') and the shape of each returned lead (name, contact details, what they want, status), which annotations do not convey.

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, zero filler, with the core purpose and ordering front-loaded before the optional filters. Nothing repeats the name or title verbatim.

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?

With no output schema, the description usefully enumerates the fields each lead returns, and pagination semantics are fully handled by the limit/offset schema. The only minor gap is that it does not state total-count or truncation behavior, but the essentials for correct invocation are present.

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 (q, from, to, limit, offset, status) is already documented with examples and an enum. The description only restates the filter categories at a high level and adds no syntax or behavioral nuance beyond the schema, which is the expected baseline here.

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?

A specific verb and resource ('List the leads your AI team captured') plus the returned fields and ordering ('newest first') make the operation unmistakable. The resource is distinct from siblings such as list_pending_approvals or list_conversations, so an agent can route correctly 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 Guidelines4/5

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

It states the three filtering dimensions (status, search text, captured-date range), which tells an agent how to narrow results in practice. It stops short of naming when to prefer an alternative tool or when not to use it, so it clears the 'clear context' bar but not the explicit-alternatives bar.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All NeoMind tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?