Kommo Kiro MCP

Overview Schema Source Related Servers Discussions Admin

list_pipelines

Read-onlyIdempotent

Fetch all sales pipelines in the Kommo CRM account to obtain pipeline and stage IDs required by most lead tools. Results are cached for 10 minutes.

Instructions

List all sales pipelines in the account. Read-only. Returns pipeline objects (id, name, sort, embedded stages as provided by Kommo). Results are cached for 10 minutes, so very recent changes may not show. Start here to obtain the pipeline_id and stage IDs used by most lead tools.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes	Returned entities.

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": "Pipelines, as {items: [pipeline, ...]}.",
+  "properties": {
+    "items": {
+      "description": "Returned entities.",
+      "items": {
+        "additionalProperties": true,
+        "description": "A sales 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"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}

First observedv1.0.0Oct 3, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavioral context the agent cannot get elsewhere: a 10-minute result cache with a stated staleness consequence, plus the shape of returned pipeline objects including embedded stages.

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, front-loaded with the purpose, then safety, then return/behavioral caveats, then usage. Every sentence carries information an agent needs; nothing is redundant with the structured fields.

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?

For a zero-parameter listing tool with an output schema, the description supplies exactly the missing pieces: caching/staleness, the ID values downstream tools consume, and its role as the entry point. Nothing an agent needs to call it correctly is absent.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The description correctly implies a no-argument full listing.

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 ("List all sales pipelines in the account") and immediately scopes it as read-only, clearly separating it from sibling mutators like create_pipeline/update_pipeline and from the adjacent list_stages.

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?

"Start here to obtain the pipeline_id and stage IDs used by most lead tools" gives explicit entry-point guidance and ties the output to downstream lead tools. It stops short of naming an alternative or stating a when-not condition, so it is strong but not exhaustive.

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