Kommo Kiro MCP

Overview Schema Source Related Servers Discussions Admin

create_lead

Create a new lead in Kommo with a name, price, tags, and pipeline stage. Missing tags are created automatically; returns the new lead object.

Instructions

Create one lead in Kommo. Not idempotent: each call creates a new lead. Tag names that do not exist yet are created automatically. Returns the created lead object. To create the contact and company in the same call, use create_lead_complex.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Lead name (title of the deal).
`tags`	No	Tag names to attach, e.g. ["vip", "web"]. Created if missing.
`price`	No	Deal value in the account currency, e.g. 1500.
`stage_id`	No	Stage (status) to place the lead in. Get IDs from list_stages. Omit for the first stage of the pipeline.
`pipeline_id`	No	Pipeline to create the lead in. Get IDs from list_pipelines. Omit to use the account default.
`responsible_user_id`	No	Kommo user ID to assign as owner. Omit for the default user.
`custom_fields_values`	No	Lead custom field values in Kommo API v4 format: a list of objects, each addressing a field by `field_id` (from list_custom_fields) or by system `field_code`, plus `values`: [{value}] (select-type fields also take enum_id or enum_code). Example: [{"field_id": 123456, "values": [{"value": "Website"}]}].

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.

Changed2 schema fields changedv1.0.3Oct 3, 2026

addedInput schema / properties / custom_fields_values

Added value: +{
+  "description": "Lead custom field values in Kommo API v4 format: a list of objects, each addressing a field by `field_id` (from list_custom_fields) or by system `field_code`, plus `values`: [{value}] (select-type fields also take enum_id or enum_code). Example: [{\"field_id\": 123456, \"values\": [{\"value\": \"Website\"}]}].",
+  "items": {
+    "properties": {
+      "field_code": {
+        "description": "Field system code, e.g. UTM_SOURCE. Use this or field_id.",
+        "type": "string"
+      },
+      "field_id": {
+        "description": "Custom field ID from list_custom_fields. Use this or field_code.",
+        "type": "integer"
+      },
+      "values": {
+        "description": "One or more values to store, each as {value} (plus enum_id/enum_code).",
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "values"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "The created lead (id, name and request_id at minimum).",
+  "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"
+}

Changed6 schema fields changedOct 3, 2026

changedInput schema / properties / name / description

Previous value: -"Lead name"New value: +"Lead name (title of the deal)."

changedInput schema / properties / pipeline_id / description

Previous value: -"Target pipeline ID"New value: +"Pipeline to create the lead in. Get IDs from list_pipelines. Omit to use the account default."

changedInput schema / properties / price / description

Previous value: -"Deal value"New value: +"Deal value in the account currency, e.g. 1500."

changedInput schema / properties / responsible_user_id / description

Previous value: -"Assigned user ID"New value: +"Kommo user ID to assign as owner. Omit for the default user."

changedInput schema / properties / stage_id / description

Previous value: -"Target stage ID"New value: +"Stage (status) to place the lead in. Get IDs from list_stages. Omit for the first stage of the pipeline."

changedInput schema / properties / tags / description

Previous value: -"Tag names"New value: +"Tag names to attach, e.g. [\"vip\", \"web\"]. Created if missing."

First observedv1.0.0Oct 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare idempotentHint=false, readOnlyHint=false, and destructiveHint=false, so the write-safety profile is covered. The description adds genuine behavioral context beyond them: tag names that don't exist are created automatically (a side effect not visible in annotations) and the explicit 'each call creates a new lead' non-idempotency warning.

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?

Four short sentences, front-loaded with the core action and followed by the most decision-relevant caveats (idempotency, tag creation, alternative tool). 'Returns the created lead object' is mildly redundant given an output schema exists, but nothing else is wasted.

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 7-parameter create tool with full schema coverage, annotations, and an output schema, the description covers the essential behavioral facts (non-idempotent, tag auto-creation, alternative tool) and need not explain return values. It omits permission/account requirements, but the coverage is otherwise solid.

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 every parameter is already documented in the schema, including the auto-creation of tags and the custom_fields_values format. The description adds no format, syntax, or constraint detail beyond what the schema provides, so the baseline 3 applies.

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 states a specific verb+resource ('Create one lead in Kommo') and immediately scopes it as singular, distinguishing it from bulk creation. It also names the sibling that handles the broader case (create_lead_complex), so an agent can choose correctly without opening either schema.

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?

It gives an explicit routing rule: use create_lead_complex when you also need to create the contact and company in the same call. That is clear context for the primary alternative, but there are no stated exclusions or guidance for other related siblings (update_lead, bulk_update_leads, move_lead_stage).

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