Kommo Kiro MCP

Overview Schema Source Related Servers Discussions Admin

list_leads

Read-onlyIdempotent

Retrieve CRM leads, optionally filtered by pipeline and stage, returning read-only records with embedded contacts and tags for reporting or follow-up.

Instructions

List leads, optionally filtered by pipeline and stage. Read-only. Returns an array of lead objects with embedded contacts and tags, up to limit items (follows Kommo pagination when limit exceeds 50). To fetch custom fields for one lead, use get_lead.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of leads to return. Default 50.
`stage_id`	No	Only leads in this stage. Ignored unless pipeline_id is also set. Get IDs from list_stages.
`pipeline_id`	No	Only leads in this pipeline. Get IDs from list_pipelines.

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": "Leads, as {items: [lead, ...]}.",
+  "properties": {
+    "items": {
+      "description": "Returned entities.",
+      "items": {
+        "additionalProperties": true,
+        "description": "A Kommo lead. Fields beyond those listed (embedded contacts, companies, etc.) may appear. Write operations may return only id, name, updated_at and request_id.",
+        "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"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedOct 3, 2026

changedInput schema / properties / limit / description

Previous value: -"Max leads to return"New value: +"Maximum number of leads to return. Default 50."

changedInput schema / properties / pipeline_id / description

Previous value: -"Filter by pipeline ID"New value: +"Only leads in this pipeline. Get IDs from list_pipelines."

changedInput schema / properties / stage_id / description

Previous value: -"Filter by stage ID"New value: +"Only leads in this stage. Ignored unless pipeline_id is also set. Get IDs from list_stages."

First observedv1.0.0Oct 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'Read-only' is partly redundant. The description does add genuinely non-annotated behavior: pagination kicks in when limit exceeds 50 (Kommo pagination), and results embed contacts and tags. It does not mention rate limits or ordering guarantees.

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?

Three compact sentences, front-loaded with the verb/resource and scope, then safety, then return/pagination behavior, then the alternative. No sentence is padding.

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 covering the return shape and annotations covering the safety profile, the description only needs to add scope, pagination nuance, and sibling routing — all of which it does. Nothing an agent needs to invoke this 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 description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining that pagination behavior changes above limit=50, which the schema's bare 'Maximum number of leads to return. Default 50.' does not convey. The stage/pipeline relationship itself is already documented in the schema.

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 leads') plus the scope of optional filtering by pipeline and stage, and explicitly names the sibling to use for a single lead's custom fields (get_lead). An agent can distinguish this from get_lead, list_contacts, or list_companies 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?

Clearly frames usage as a filtered list operation and routes the single-lead custom-field case to get_lead. It does not state when-not to use it (e.g., bulk retrieval limits or when to prefer bulk_update_leads for reads), so it stops 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.