Skip to main content
Glama
amocrm-kommo-mcp

amocrm-kommo-mcp

Поиск сделок

crm_search_leads
Read-onlyIdempotent

Search CRM deals by text, pipeline, stage, responsible, or creation date to find leads and get counts, budgets, and key details.

Instructions

Ищет сделки по тексту (название, телефон, e-mail, значения полей) и фильтрам: воронка, этап, ответственный, период создания. Возвращает count, total_budget и leads (id, name, price, pipeline, status, responsible, даты, tags, contact_ids, custom_fields), свежие изменения первыми. Используйте, чтобы найти сделку или список сделок; полная карточка с контактами и задачами — crm_get_lead, агрегированная аналитика — crm_pipeline_report, зависшие сделки — crm_stale_leads. Этап фильтруется только вместе с pipeline_id (иначе ошибка). Требует AMOCRM_DOMAIN и AMOCRM_TOKEN; лимит amoCRM 7 запросов/с соблюдается автоматически. Только чтение.

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

Input Schema

NameRequiredDescriptionDefault
limitNoМаксимум сделок в ответе
queryNoПоисковая строка
status_idNoЭтап (нужен вместе с pipeline_id); 142 — успешно, 143 — проиграно
created_toNoСозданы не позже этой даты
pipeline_idNoID воронки (из crm_account)
created_fromNoСозданы не раньше этой даты
responsible_user_idNoID ответственного менеджера (из crm_account)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.2.2
    • changedInput schema / properties / created_from / description
      Previous value: -"Дата ГГГГ-ММ-ДД или дата-время ISO"New value: +"Созданы не раньше этой даты"
    • changedInput schema / properties / created_to / description
      Previous value: -"Дата ГГГГ-ММ-ДД или дата-время ISO"New value: +"Созданы не позже этой даты"
    • addedInput schema / properties / limit / description
      Added value: +"Максимум сделок в ответе"
    • addedInput schema / properties / pipeline_id / description
      Added value: +"ID воронки (из crm_account)"
    • addedInput schema / properties / responsible_user_id / description
      Added value: +"ID ответственного менеджера (из crm_account)"
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive/openWorld), the description discloses the return shape and sort order (fresh changes first), a hard error condition (status_id only valid with pipeline_id), required credentials (AMOCRM_DOMAIN, AMOCRM_TOKEN), and that the amoCRM 7 req/s limit is handled automatically.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and return shape, then alternatives, then constraints and auth. Dense but efficient; the one small redundancy is restating the status_id+pipeline_id rule that the schema already carries.

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?

No output schema exists, and the description fully covers the return payload (count, total_budget, leads with their fields and ordering), the prerequisites, and the failure mode. Nothing an agent needs to call it correctly is missing.

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 coverage is 100%, so baseline is 3, but the description adds real meaning: 'query' spans name/phone/e-mail/custom field values (the schema only says 'Поисковая строка'), and it restates the status_id/pipeline_id dependency that the schema also encodes. Marginal gain over the schema is modest, hence 4 rather than 5.

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?

States a specific verb+resource ('Ищет сделки') and enumerates the searchable fields (name, phone, e-mail, field values) plus the filter set. It also names the sibling tools it is not, so an agent can separate it from crm_get_lead and crm_pipeline_report without opening any schema.

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: this tool to find a deal or a list of deals, crm_get_lead for the full card with contacts and tasks, crm_pipeline_report for aggregated analytics, crm_stale_leads for stuck deals. When-to-use and alternatives are both stated.

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