Skip to main content
Glama
depper-IA

Kommo Kiro MCP

by depper-IA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_task

Attach a follow-up task with a deadline to a Kommo lead. Use when a lead needs a scheduled call or action; each call creates a new task.

Instructions

Create a follow-up task (type 1) attached to a lead. Not idempotent: each call creates a new task. Returns the created task. Use list_tasks to review existing tasks and add_note for non-actionable remarks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesTask description shown in Kommo.
lead_idYesKommo lead ID (integer). Obtain it from list_leads or from the create_lead result.
due_dateYesDeadline as a Unix timestamp in seconds, e.g. 1767225600.
responsible_user_idNoKommo user ID responsible for the task. Omit for the default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / due_date / description
      Previous value: -"Due date as Unix timestamp"New value: +"Deadline as a Unix timestamp in seconds, e.g. 1767225600."
    • addedInput schema / properties / lead_id / description
      Added value: +"Kommo lead ID (integer). Obtain it from list_leads or from the create_lead result."
    • addedInput schema / properties / responsible_user_id / description
      Added value: +"Kommo user ID responsible for the task. Omit for the default."
    • changedInput schema / properties / text / description
      Previous value: -"Task description"New value: +"Task description shown in Kommo."
  2. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Declares 'Not idempotent: each call creates a new task' and 'Returns the created task', adding critical context beyond the annotations (which already declare idempotentHint=false, readOnlyHint=false). This warns agents against retry duplication, a key behavioral trait. It doesn't address permissions, rate limits, or failure modes, keeping it short of 5.

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-loading the action, non-idempotency warning, and routing advice. Every sentence earns its place with no redundancy.

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?

Complete for a mutation tool with annotated safety profile and fully documented schema. It covers scope, side-effect behavior, return value, and sibling routing. No output schema needed since it states the return. Nothing an agent needs to call correctly is missing.

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 the schema already documents all four parameters fully. The description adds no parameter-level syntax or format details beyond what the schema provides. Baseline 3 applies when schema does the heavy lifting.

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 ('Create') and resource ('follow-up task (type 1) attached to a lead'), and distinguishes from sibling list_tasks. The '(type 1)' detail signals a specific task subtype, which no sibling covers.

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 to list_tasks for review and add_note for non-actionable remarks, providing direct alternatives for the closest sibling tools. When-to-use is clear without needing to read other definitions.

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