Skip to main content
Glama
ilyaberdysh

amocrm-mcp

by ilyaberdysh

get_leads

Retrieve leads from AmoCRM with filters for pipeline, status, dates, price, and more. Supports pagination and related entities like contacts and companies.

Instructions

Получает сделки из CRM с фильтрами. Все даты — unix timestamp (секунды). Используй closed_at_from/closed_at_to для фильтра по дате ЗАКРЫТИЯ. date_from/date_to — только для даты СОЗДАНИЯ. Максимум 200 записей за запрос. ВНИМАНИЕ: фильтры price_from/price_to могут конфликтовать с status_ids — для фильтрации активных сделок по цене используй count_and_sum_leads с exclude_closed=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pipeline_idNoID воронки
status_idsNoID этапов/статусов (получи из get_pipelines)
responsible_user_idsNoID ответственных менеджеров
created_byNoID пользователей, создавших сделку
date_fromNoНачало периода по дате СОЗДАНИЯ (unix timestamp)
date_toNoКонец периода по дате СОЗДАНИЯ (unix timestamp)
updated_at_fromNoНачало периода по дате ИЗМЕНЕНИЯ (unix timestamp)
updated_at_toNoКонец периода по дате ИЗМЕНЕНИЯ (unix timestamp)
closed_at_fromNoНачало периода по дате ЗАКРЫТИЯ (unix timestamp). Для 'сделки закрытые в марте'.
closed_at_toNoКонец периода по дате ЗАКРЫТИЯ (unix timestamp)
price_fromNoМинимальная сумма сделки
price_toNoМаксимальная сумма сделки
queryNoПоиск по названию сделки
order_byNoПоле сортировки
order_dirNoНаправление сортировки
with_contactsNoВключить связанные контакты
with_companiesNoВключить связанные компании
with_loss_reasonNoВключить причину отказа
with_tasksNoВключить задачи по сделке
with_catalog_elementsNoВключить товары из каталога
limitNoМаксимум сделок (по умолчанию 200, это максимум API)
pageNoНомер страницы для пагинации. По умолчанию 1. Если pipeline содержит более 200 сделок, используй page=2 для выборки записей 201+.
Behavior4/5

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

No annotations are provided, so the description bears full responsibility. It discloses max 200 records, date format requirements, pagination, and a conflict scenario. Could mention permissions or empty results, but covers key behaviors well.

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?

Six sentences covering essential info, each sentence adds value. Slightly verbose but effective. Could be more concise, but no unnecessary fluff.

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 tool with 22 parameters and no output schema, the description explains key behaviors (date filter differences, conflict, limit, pagination). It covers most important aspects for agent usage, though lacks return structure details.

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%, baseline 3. The description adds value by clarifying the distinction between closed_at and date filters, the conflict warning, and pagination details, going beyond the schema's field descriptions.

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?

The description clearly states the tool retrieves deals from CRM with filters, specifying date formats and conflict warnings. It distinguishes itself from siblings by detailing unique parameter behaviors.

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?

Provides explicit guidance on when to use date filters, warns about conflicts between price filters and status_ids, and directs to an alternative tool (count_and_sum_leads) for specific cases. Also explains pagination and limit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ilyaberdysh/amocrm-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server