Kommo Kiro MCP

Overview Schema Source Related Servers Discussions Admin

update_pipeline

Idempotent

Rename an existing Kommo CRM pipeline by providing its ID and new name. Returns the updated pipeline; use a separate tool to change stages.

Instructions

Rename an existing pipeline. Only the name can be changed with this tool. Returns the updated pipeline. Safe to repeat. Clears the pipelines cache. To change a stage use update_stage.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	New pipeline name.
`pipeline_id`	Yes	Kommo pipeline ID (integer). Obtain it from list_pipelines.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Pipeline ID.
`name`	No	Pipeline name.
`sort`	No	Sort order.
`is_main`	No	Whether this is the main pipeline.
`_embedded`	No	Embedded resources.
`account_id`	No	Kommo account ID.
`is_archive`	No	Whether the pipeline is archived.
`is_unsorted_on`	No	Whether the Incoming leads stage is enabled.

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 pipeline.",
+  "properties": {
+    "_embedded": {
+      "additionalProperties": true,
+      "description": "Embedded resources.",
+      "properties": {
+        "statuses": {
+          "description": "Embedded statuses.",
+          "items": {
+            "additionalProperties": true,
+            "description": "A pipeline stage (status).",
+            "properties": {
+              "account_id": {
+                "description": "Kommo account ID.",
+                "type": [
+                  "integer",
+                  "null"
+                ]
+              },
+              "color": {
+                "description": "Hex color.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "id": {
+                "description": "Stage ID.",
+                "type": "integer"
+              },
+              "is_editable": {
+                "description": "Whether the stage can be edited.",
+                "type": [
+                  "boolean",
+                  "null"
+                ]
+              },
+              "name": {
+                "description": "Stage name.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "pipeline_id": {
+                "description": "Parent pipeline ID.",
+                "type": [
+                  "integer",
+                  "null"
+                ]
+              },
+              "sort": {
+                "description": "Sort order.",
+                "type": [
+                  "integer",
+                  "null"
+                ]
+              },
+              "type": {
+                "description": "0 for regular stages, 1 for unsorted.",
+                "type": [
+                  "integer",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "account_id": {
+      "description": "Kommo account ID.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "Pipeline ID.",
+      "type": "integer"
+    },
+    "is_archive": {
+      "description": "Whether the pipeline is archived.",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "is_main": {
+      "description": "Whether this is the main pipeline.",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "is_unsorted_on": {
+      "description": "Whether the Incoming leads stage is enabled.",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Pipeline name.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sort": {
+      "description": "Sort order.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedOct 3, 2026
- addedInput schema / properties / name / description
```
Added value: +"New pipeline name."
```
- addedInput schema / properties / pipeline_id / description
```
Added value: +"Kommo pipeline ID (integer). Obtain it from list_pipelines."
```
First observedv1.0.0Oct 3, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (idempotentHint, destructiveHint=false, readOnlyHint=false), and 'Safe to repeat' largely restates idempotency. However, 'Clears the pipelines cache' is a genuine side-effect disclosure not present in annotations, and 'Returns the updated pipeline' confirms the mutation result. Solid added value, minor redundancy.

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?

Five short, front-loaded sentences with zero filler. The scope restriction and alternative routing appear before less critical details like cache behavior.

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?

An output schema exists, yet the description still notes what is returned, and it covers the mutation's side effect, idempotency, and the sibling alternative. Nothing needed to invoke this two-parameter rename tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are self-documented (baseline 3). The description adds a constraint beyond the schema: only 'name' is mutable, which is not derivable from a schema that marks both fields as required. That extra semantic boundary earns a bump.

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 ('Rename an existing pipeline') and immediately bounds the scope with 'Only the name can be changed with this tool.' It also names the sibling update_stage for stage changes, so the agent can distinguish it 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the when-not condition ('Only the name can be changed') and routes the alternative case ('To change a stage use update_stage'). Combined with the schema note that pipeline_id comes from list_pipelines, the selection path is unambiguous.

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