Kommo Kiro MCP

Overview Schema Source Related Servers Discussions Admin

create_pipeline

Create a new Kommo CRM sales pipeline by name to organize leads into stages. Each call adds a separate pipeline; add stages afterward to complete setup.

Instructions

Create a new sales pipeline with the given name (sort order 99). Not idempotent: each call creates another pipeline. Returns the created pipeline. Add stages afterwards with create_stage. Clears the pipelines cache.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Pipeline name, e.g. "Enterprise".

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 created 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"
+}

Changed1 schema field changedOct 3, 2026
- changedInput schema / properties / name / description
```
Previous value: -"Pipeline name"New value: +"Pipeline name, e.g. \"Enterprise\"."
```
First observedv1.0.0Oct 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description still adds real value beyond them: the concrete consequence of non-idempotency ('each call creates another pipeline'), the default sort order of 99, and the side effect 'Clears the pipelines cache.' It omits permission/auth requirements and duplicate-name behavior.

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?

Four short sentences, each carrying distinct information (creation, non-idempotency, return value, follow-up tool, cache side effect). The core action is front-loaded with zero filler.

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?

With an output schema present, return values need no elaboration, yet the description still notes it returns the created pipeline. Non-idempotency, cache invalidation, and the create_stage follow-up are all covered, leaving only minor gaps such as duplicate-name handling and required permissions.

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 single parameter already has a documented example ('Enterprise'), so the schema carries the parameter semantics. The description mentions the name and the implicit sort order, but adds no syntax or constraint details beyond the schema. Baseline 3 is appropriate.

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 ('Create a new sales pipeline') plus the scope of the operation (name, default sort order 99). It is clearly distinguishable from sibling tools like update_pipeline, list_pipelines, and create_stage.

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 workflow cue ('Add stages afterwards with create_stage') and warns that repeated calls are not idempotent, which helps an agent decide whether to retry. It does not explicitly state when to prefer update_pipeline over this tool, but the create-vs-update split is implied by the verb.

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