Kommo Kiro MCP

Overview Schema Source Related Servers Discussions Admin

update_lead

Idempotent

Modify fields on an existing Kommo lead with a PATCH request; omitted fields stay unchanged and the updated lead is returned. Change stages with move_lead_stage or edit many leads in bulk.

Instructions

Update fields on an existing lead by sending fields as the body of a Kommo API v4 PATCH /leads/{id}. Returns the updated lead. Overwrites the given values; omitted fields are untouched. For a stage change prefer move_lead_stage; for several leads use bulk_update_leads.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fields`	Yes	Raw Kommo v4 lead fields to change, passed through unchanged. Common keys: name (string), price (integer), status_id (stage ID), pipeline_id, responsible_user_id, custom_fields_values (array of {field_id, values: [{value}]}), _embedded.tags (full replacement list of {id}). Example: {"name": "Acme renewal", "price": 2000}.
`lead_id`	Yes	Kommo lead ID (integer). Obtain it from list_leads or from the create_lead result.

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 updated lead as returned by Kommo.",
+  "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"
+}

Changed2 schema fields changedOct 3, 2026

changedInput schema / properties / fields / description

Previous value: -"Fields to update"New value: +"Raw Kommo v4 lead fields to change, passed through unchanged. Common keys: name (string), price (integer), status_id (stage ID), pipeline_id, responsible_user_id, custom_fields_values (array of {field_id, values: [{value}]}), _embedded.tags (full replacement list of {id}). Example: {\"name\": \"Acme renewal\", \"price\": 2000}."

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."

First observedv1.0.0Oct 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds genuinely useful semantics beyond them: partial-update behavior ('Overwrites the given values; omitted fields are untouched') and that `fields` is passed through raw to the Kommo v4 PATCH endpoint. It does not cover auth requirements or failure behavior, which keeps it short of a 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 short sentences, zero filler, with the core action and mutation semantics front-loaded before the sibling routing hints. Every sentence earns its place.

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?

An output schema exists, so return-value explanation is unnecessary, and the description correctly notes the updated lead is returned. Required parameters, mutation semantics, and sibling routing are all covered for a two-parameter tool with a nested passthrough object; only edge cases like invalid field names or partial failure are unaddressed.

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% and the `fields` parameter already documents common keys, custom_fields_values shape, tag replacement semantics, and an example. The description only adds that `fields` is sent as the request body unchanged, which is marginal beyond the schema. Baseline 3 applies when the 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 and resource ('Update fields on an existing lead') and names the exact underlying operation (PATCH /leads/{id}), so the agent knows precisely what is being mutated. It also explicitly distinguishes itself from the two closest siblings, move_lead_stage and bulk_update_leads.

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?

Gives explicit routing rules: use move_lead_stage for a stage change and bulk_update_leads for several leads. This is a when-to-use-this-vs-alternatives statement with the selecting condition attached, leaving nothing to inference.

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