Skip to main content
Glama
penmadebykisss

amocrm-kommo-mcp

by penmadebykisss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Поставить задачу

crm_create_task

Create a call or meeting task with due date and responsible manager, linked to a deal, contact, company, or unlinked; returns task_id and due.

Instructions

Ставит задачу со сроком: звонок или встреча, привязанная к сделке, контакту или компании (или без привязки), с ответственным. Дата без времени означает 18:00 по часовому поясу сервера; для точного времени передайте ISO с зоной, например 2026-10-01T11:00:00+03:00. Возвращает task_id и due. Закрыть задачу — crm_complete_task, посмотреть задачи — crm_tasks. Требует AMOCRM_DOMAIN и AMOCRM_TOKEN; лимит amoCRM 7 запросов/с соблюдается автоматически. Изменяет данные в CRM: покажите пользователю, что будет записано, и получите согласие.

Input Schema

NameRequiredDescriptionDefault
dueYesСрок: ГГГГ-ММ-ДД или дата-время ISO, например 2026-10-01T15:00:00+03:00
textYesТекст задачи, например «Перезвонить и обсудить КП»
entity_idNoID сделки, контакта или компании; без него задача не привязана
task_typeNoТип: звонок или встреча; по умолчанию звонок
entity_typeNoТип сущности: сделка, контакт или компанияleads
responsible_user_idNoID ответственного менеджера (из crm_account)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.2.2
    • addedInput schema / properties / entity_id / description
      Added value: +"ID сделки, контакта или компании; без него задача не привязана"
    • addedInput schema / properties / entity_type / description
      Added value: +"Тип сущности: сделка, контакт или компания"
    • addedInput schema / properties / responsible_user_id / description
      Added value: +"ID ответственного менеджера (из crm_account)"
    • addedInput schema / properties / text / description
      Added value: +"Текст задачи, например «Перезвонить и обсудить КП»"
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true, but the description adds real behavior: date-only input resolves to 18:00 server timezone, ISO with zone for exact time, returns task_id and due, required env vars AMOCRM_DOMAIN/AMOCRM_TOKEN, the amoCRM 7 req/s limit handled automatically, and the obligation to confirm the write with the user.

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 the core action, then grouped details (date semantics, return values, sibling routing, auth/rate limits, consent). Every sentence carries information, though the definition is dense and could be slightly tighter.

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, yet the description names the returned fields (task_id, due). With 6 params fully schema-documented, annotations covering safety, and auth/rate-limit/consent behavior disclosed, an agent has everything needed to invoke it correctly.

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 the baseline is 3, but the description adds meaning beyond the schema: the 18:00 default for a date-only due value and the ISO-with-timezone format are not documented in the schema itself. This genuinely clarifies the most error-prone parameter.

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 (Ставит) plus resource (задачу) and enumerates the full scope: task type (звонок/встреча), the three binding targets or none, and the responsible party. It is immediately distinguishable from crm_complete_task and crm_tasks, which it names.

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?

Explicitly routes the agent to siblings: 'Закрыть задачу — crm_complete_task, посмотреть задачи — crm_tasks', and states the consent requirement before mutating CRM data. It does not state exclusions (e.g. when not to create a task), so it falls just short of 5.

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

Deploy Server

Other Tools