Kommo Kiro MCP

Overview Schema Source Related Servers Discussions Admin

move_lead_stage

Idempotent

Move a Kommo lead to another stage by setting its stage_id (and pipeline_id when needed) and return the updated lead. Use for pipeline moves instead of update_lead.

Instructions

Move a lead to another stage by setting its status_id (and optionally pipeline_id). Returns the updated lead. Use this instead of update_lead for pipeline moves. Pass pipeline_id when moving to a stage in a different pipeline.

Input Schema

TableJSON Schema

Name	Required	Description
`lead_id`	Yes	Kommo lead ID (integer). Obtain it from list_leads or from the create_lead result.
`stage_id`	Yes	Target stage ID. Get IDs from list_stages.
`pipeline_id`	No	Target pipeline ID. Only needed when the stage belongs to a different pipeline than the lead's current one.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Lead ID.
`name`	No	Lead name.
`price`	No	Lead budget.
`_links`	No	HAL links as returned by Kommo (self, next, ...).
`group_id`	No	ID of the responsible user's group.
`_embedded`	No	Embedded tags, contacts and companies.
`closed_at`	No	Closing time, Unix seconds, or null.
`status_id`	No	Current stage ID.
`account_id`	No	Kommo account ID.
`created_at`	No	Creation time, Unix seconds.
`created_by`	No	ID of the user who created it.
`is_deleted`	No	Whether the lead is deleted.
`updated_at`	No	Last update time, Unix seconds.
`updated_by`	No	ID of the user who last updated it.
`pipeline_id`	No	Pipeline ID.
`loss_reason_id`	No	Loss reason ID, or null.
`closest_task_at`	No	Next task deadline, Unix seconds, or null.
`responsible_user_id`	No	ID of the responsible Kommo user.
`custom_fields_values`	No	Custom field values in Kommo format: objects with field_id, field_code and values.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.3Oct 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "The lead after the stage change.",
+  "properties": {
+    "_embedded": {
+      "additionalProperties": true,
+      "description": "Embedded tags, contacts and companies.",
+      "properties": {
+        "tags": {
+          "description": "Embedded tags.",
+          "items": {
+            "additionalProperties": true,
+            "description": "A Kommo tag.",
+            "properties": {
+              "color": {
+                "description": "Tag color, or null.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "id": {
+                "description": "Tag ID.",
+                "type": "integer"
+              },
+              "name": {
+                "description": "Tag name.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "_links": {
+      "additionalProperties": true,
+      "description": "HAL links as returned by Kommo (self, next, ...).",
+      "properties": {},
+      "type": "object"
+    },
+    "account_id": {
+      "description": "Kommo account ID.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "closed_at": {
+      "description": "Closing time, Unix seconds, or null.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "closest_task_at": {
+      "description": "Next task deadline, Unix seconds, or null.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "created_at": {
+      "description": "Creation time, Unix seconds.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "created_by": {
+      "description": "ID of the user who created it.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "custom_fields_values": {
+      "description": "Custom field values in Kommo format: objects with field_id, field_code and values.",
+      "items": {
+        "additionalProperties": true,
+        "description": "One custom field with its values.",
+        "properties": {},
+        "type": "object"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "group_id": {
+      "description": "ID of the responsible user's group.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "Lead ID.",
+      "type": "integer"
+    },
+    "is_deleted": {
+      "description": "Whether the lead is deleted.",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "loss_reason_id": {
+      "description": "Loss reason ID, or null.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Lead name.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "pipeline_id": {
+      "description": "Pipeline ID.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "price": {
+      "description": "Lead budget.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "responsible_user_id": {
+      "description": "ID of the responsible Kommo user.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "status_id": {
+      "description": "Current stage ID.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "updated_at": {
+      "description": "Last update time, Unix seconds.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "updated_by": {
+      "description": "ID of the user who last updated it.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedOct 3, 2026

changedInput schema / properties / lead_id / description

Previous value: -"The lead ID"New value: +"Kommo lead ID (integer). Obtain it from list_leads or from the create_lead result."

changedInput schema / properties / pipeline_id / description

Previous value: -"Target pipeline ID (optional if same pipeline)"New value: +"Target pipeline ID. Only needed when the stage belongs to a different pipeline than the lead's current one."

changedInput schema / properties / stage_id / description

Previous value: -"Target stage ID"New value: +"Target stage ID. Get IDs from list_stages."

First observedv1.0.0Oct 3, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety and repeatability are covered structurally. The description adds only that it returns the updated lead and that it is the pipeline-move path; it says nothing extra about side effects like stage-history entries or notifications. Adequate but not rich.

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 tight sentences, front-loaded with the action, then the return, then the routing rule. No filler and every sentence carries distinct information.

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?

With an output schema, full annotations, and 100% schema description coverage, the description only needs to cover routing and scope, which it does. Nothing an agent needs to call this 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 description coverage is 100%, so lead_id, stage_id, and pipeline_id are already documented in the schema; baseline is 3. The description lightly reinforces pipeline_id's conditional nature, but it also refers to 'status_id' while the actual parameter is named 'stage_id', which adds a small naming ambiguity rather than clarity.

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 ('Move a lead to another stage') plus the mechanism ('by setting its status_id'), and explicitly distinguishes itself from the sibling update_lead. An agent can tell what this does without opening the 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?

Names the alternative it replaces ('Use this instead of update_lead for pipeline moves') and gives the precise condition for the optional parameter ('Pass pipeline_id when moving to a stage in a different pipeline'). Routing and conditional usage are both explicit.

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