Skip to main content
Glama
amocrm-mcp-prm

amocrm-mcp-prm

by m00zz

list_leads

Search and list amoCRM deals using filters like pipeline, status, responsible user, and date ranges. Supports sorting and compact view for readable results.

Instructions

Search and list deals (leads) in amoCRM. Filters: pipeline, statuses, responsible users, created/updated/closed date ranges, full-text search. Supports sorting. Set compact=true for a trimmed, readable list. For counts and breakdowns use leads_summary instead of paging through leads.

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
idsNoFetch specific lead IDs
pageNoPage number (default 1)
withNoRelated entities to embed in response
limitNoItems per page (max 250, default 50)
queryNoSearch query across lead name, contacts, companies
compactNoReturn a trimmed view: readable dates, custom fields as name→value, no cookies/tracking noise. Recommended for lists.
order_byNoSort field (API default: oldest first)
statusesNoFilter by statuses: array of {pipeline_id, status_id}
closed_toNoClosed at or before this date
order_dirNoSort direction (default desc when order_by is set)
created_toNoCreated at or before this date
updated_toNoUpdated at or before this date
closed_fromNoClosed at or after this date
pipeline_idNoFilter by pipeline ID
created_fromNoCreated at or after this date
updated_fromNoUpdated at or after this date
responsible_user_idsNoFilter by responsible user IDs (see list_users)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it does disclose that compact=true returns a trimmed view with readable dates and no tracking noise, which is genuinely useful behavioral context. However, it says nothing about pagination semantics beyond the schema, result shape, or access requirements, which matter for a 17-parameter list tool with no output schema.

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?

Three compact sentences, front-loaded with purpose, then capability, then the two routing hints. Nothing is redundant and no sentence merely restates the tool name.

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 17-parameter, zero-required, well-documented-schema query tool this covers purpose, alternatives, and the compact flag adequately. Minor gaps remain around pagination expectations and what the response looks like, but the exhaustive schema compensates for most of it.

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?

Schema description coverage is 100%, so the baseline is 3; the description adds a little by listing the filter families (pipeline, statuses, responsible, date ranges, full-text) and by explaining the intended use of compact=true rather than merely its format. It does not add syntax or interaction details beyond the schema.

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?

Opens with a specific verb+resource ('Search and list deals (leads)') plus the system it lives in (amoCRM), then enumerates the filter dimensions and sorting support. An agent can immediately tell this is the paged/filtered retrieval tool rather than a summary or single-record getter.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly routes the agent away from paging with 'For counts and breakdowns use leads_summary instead of paging through leads', and recommends compact=true for readable lists. Both a when-to-use and a when-not-to-use alternative are stated.

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