Kommo Kiro MCP

Overview Schema Source Related Servers Discussions Admin

list_tasks

Read-onlyIdempotent

Fetch Kommo CRM tasks for a lead, all tasks, or only overdue items; supports pagination and limit up to 250 for read-only reporting and follow-ups.

Instructions

List tasks, optionally for one lead or only overdue ones. Read-only. Returns an array (Kommo default page size unless limit is set, max 250); pass page for paginated output with a has_next flag. Overdue means deadline at or before now and not completed.

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	Tasks per page, max 250. Omit for Kommo's default (50).
`lead_id`	No	Only tasks attached to this lead. Omit for all tasks.
`filter_overdue`	No	If true, only uncompleted tasks whose deadline has passed.

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.

Changed3 schema fields changedv1.0.3Oct 3, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "Tasks per page, max 250. Omit for Kommo's default (50).",
+  "maximum": 250,
+  "minimum": 1,
+  "type": "integer"
+}

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": "Tasks, as {items: [task, ...]}. 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 task.",
+        "properties": {
+          "_links": {
+            "additionalProperties": true,
+            "description": "HAL links as returned by Kommo (self, next, ...).",
+            "properties": {},
+            "type": "object"
+          },
+          "account_id": {
+            "description": "Kommo account ID.",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "complete_till": {
+            "description": "Deadline, Unix seconds.",
+            "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"
+            ]
+          },
+          "duration": {
+            "description": "Duration in seconds.",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "entity_id": {
+            "description": "ID of the entity the task is attached to.",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "entity_type": {
+            "description": "Entity type, e.g. leads.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "group_id": {
+            "description": "ID of the responsible user's group.",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Task ID.",
+            "type": "integer"
+          },
+          "is_completed": {
+            "description": "Whether the task is completed.",
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "responsible_user_id": {
+            "description": "ID of the responsible Kommo user.",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "result": {
+            "description": "Completion result (object or array), may be empty."
+          },
+          "task_type_id": {
+            "description": "Task type ID (1 is follow-up).",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "text": {
+            "description": "Task description.",
+            "type": [
+              "string",
+              "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 / filter_overdue / description
```
Added value: +"If true, only uncompleted tasks whose deadline has passed."
```
- addedInput schema / properties / lead_id / description
```
Added value: +"Only tasks attached to this lead. Omit for all tasks."
```
First observedv1.0.0Oct 3, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds genuine value by explaining the two return shapes (plain array vs paginated object with has_next) and defining 'overdue' precisely—details not in the annotations.

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 tight sentences front-loaded with purpose, then read-only, then return shape and the overdue definition. No 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?

An output schema exists, so return values needn't be explained, yet the description still helpfully clarifies the array-vs-paginated duality that a caller must handle. The only gap is the absence of usage routing against alternatives, which is minor here.

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 coverage is 100%, so every parameter is already documented in the schema with equal or greater detail (e.g., default 50, max 250, 1-based page). The description restates pagination behavior but adds nothing beyond the schema, so 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 (List) and resource (tasks), plus the two filtering dimensions (lead, overdue). It is clearly distinguishable from siblings like create_task or list_leads.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description covers the main filter modes (one lead, overdue) which implies when to use them, but it never names an alternative tool or states when NOT to use this one. For a list operation with no near-duplicate siblings this is acceptable but not exemplary.

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