Kommo Kiro MCP

Overview Schema Source Related Servers Discussions Admin

list_contacts

Read-onlyIdempotent

Search and read Kommo CRM contacts by name, phone, or email, with paginated results up to 250 per page. Omit the query to list recent contacts.

Instructions

Search or list contacts. Read-only. Returns an array of up to limit contacts (max 250); pass page for paginated output with a has_next flag. Pass query to match by name, phone, or email; omit it to list recent contacts. Use get_contact for one contact's full details.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	1-based page number. Omit for a plain array (first page). When set, returns {items, page, limit, has_next}; request page+1 while has_next is true.
`limit`	No	Contacts per page. Default 50, capped at 250.
`query`	No	Free-text search matched by Kommo against name, phone, and email, e.g. "Jane" or "+15551234567". Omit to list without filtering.

Output Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number returned (only when `page` was requested).
`items`	Yes	Returned entities.
`limit`	No	Page size used (only when `page` was requested).
`has_next`	No	True when another page exists (only when paginated).

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.0.3Oct 3, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum contacts to return. Default 50, capped at 100."New value: +"Contacts per page. Default 50, capped at 250."

addedInput schema / properties / limit / maximum
```
Added value: +250
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

addedInput schema / properties / page

Added value: +{
+  "description": "1-based page number. Omit for a plain array (first page). When set, returns {items, page, limit, has_next}; request page+1 while has_next is true.",
+  "minimum": 1,
+  "type": "integer"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Contacts, as {items: [contact, ...]}. With `page` set, also page, limit and has_next.",
+  "properties": {
+    "has_next": {
+      "description": "True when another page exists (only when paginated).",
+      "type": "boolean"
+    },
+    "items": {
+      "description": "Returned entities.",
+      "items": {
+        "additionalProperties": true,
+        "description": "A Kommo contact. Phone and email live in custom_fields_values.",
+        "properties": {
+          "_embedded": {
+            "additionalProperties": true,
+            "description": "Embedded tags 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"
+            ]
+          },
+          "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"
+            ]
+          },
+          "first_name": {
+            "description": "First name.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "group_id": {
+            "description": "ID of the responsible user's group.",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Contact ID.",
+            "type": "integer"
+          },
+          "last_name": {
+            "description": "Last name.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Full name.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "responsible_user_id": {
+            "description": "ID of the responsible Kommo user.",
+            "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"
+    },
+    "limit": {
+      "description": "Page size used (only when `page` was requested).",
+      "type": "integer"
+    },
+    "page": {
+      "description": "Page number returned (only when `page` was requested).",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedOct 3, 2026

addedInput schema / properties / limit / description

Added value: +"Maximum contacts to return. Default 50, capped at 100."

changedInput schema / properties / query / description

Previous value: -"Search query (name, phone, or email)"New value: +"Free-text search matched by Kommo against name, phone, and email, e.g. \"Jane\" or \"+15551234567\". Omit to list without filtering."

First observedv1.0.0Oct 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds real behavioral context: the two distinct return shapes (plain array vs {items, page, limit, has_next}), the 250 cap, and the page+1-while-has_next iteration contract.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences, front-loaded with the verb and read-only status before the branching rules. Minor redundancy: the 250 cap and 'max 250' appear in both description and schema description.

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 and rich annotations, the description need not explain return fields; it still supplies the pagination loop contract and mode distinction that matter for correct invocation. Nothing needed to call 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 coverage is 100%, so the baseline would be 3, but the description adds cross-parameter semantics the schema cannot: the query/omit duality and the mode switch triggered by supplying page. It stops short of adding anything the schema lacks about limit's default or range.

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 both verbs and the resource ('Search or list contacts') and explicitly contrasts itself with the sibling get_contact for single-record retrieval. An agent can pick between list_contacts and get_contact 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?

Gives explicit branch conditions: pass `query` to match by name/phone/email, omit it to list recent contacts, pass `page` for paginated output. It also names the alternative tool for the single-contact case, covering both when-to-use and when-not-to-use.

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