Kommo Kiro MCP

Overview Schema Source Related Servers Discussions Admin

add_tag

Idempotent

Attach a tag to a Kommo lead by name, creating it if missing while keeping existing tags. Safe to repeat and returns the updated lead.

Instructions

Attach a tag to a lead by name. Creates the tag if it does not exist. Reads the lead's current tags and writes back the full list plus the new one, so existing tags are kept. Safe to repeat. Returns the updated lead. See list_tags for existing tag names.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lead_id`	Yes	Kommo lead ID (integer). Obtain it from list_leads or from the create_lead result.
`tag_name`	Yes	Exact tag name (case-sensitive), e.g. "vip".

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 tag was added.",
+  "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

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 / tag_name / description

Added value: +"Exact tag name (case-sensitive), e.g. \"vip\"."

First observedv1.0.0Oct 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare non-readOnly, idempotent and non-destructive, yet the description adds real behavioral detail beyond them: it upserts the tag if missing, and it performs a read-modify-write that preserves existing tags. It stops short of covering permissions, failure behavior or concurrency concerns.

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?

Six short sentences, front-loaded with the action and its upsert/preservation semantics, and every sentence carries distinct information (what it does, side effects, idempotency, return, sibling pointer).

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 present, return values need no elaboration, and the annotations cover the safety profile; the description supplies the remaining non-obvious semantics (upsert, full-list rewrite, idempotency). Nothing needed to invoke it 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 both parameters are already documented in the schema (including case-sensitivity and how to obtain lead_id). The description only reinforces that the tag is addressed by name; 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?

States a specific verb (attach) and resource (tag to a lead) plus the qualifying 'by name'. It is clearly distinguishable from remove_tag, list_tags and get_lead without opening any 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?

Gives a concrete routing hint ('See list_tags for existing tag names') and states that the operation is safe to repeat, which tells the agent it need not check for duplicates first. It does not explicitly contrast with remove_tag or state when not to use it, so it falls short of full when/when-not guidance.

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