Kommo MCP Server

add_pipeline_stage

Add a new stage to an existing pipeline in Kommo. Provide the pipeline ID and stage name; optionally set color and sorting order.

Instructions

Add a new stage (status) to an existing pipeline in Kommo.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pipeline_id": "<pipeline_id>",
      "name": "<name>"
    },
    "name": "add_pipeline_stage"
  }
}

Input Schema

Name	Required	Description
`pipeline_id`	Yes	ID of the pipeline
`name`	Yes	Name of the new stage (status)
`color`	No	Background color of the stage in hex format (e.g. #fffd7f)
`sort`	No	Sorting order (position) of the stage

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 26, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, and the description only states 'Add' which implies a mutation. It does not disclose side effects (e.g., ordering changes), required permissions, error conditions, or behavior on duplicate names.

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?

Description is a single concise sentence with no redundant information. It front-loads the core purpose, but the structure is minimal and lacks any secondary details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is provided, and the description does not mention return values, error handling, or prerequisites (e.g., pipeline must exist). Given the tool has 4 parameters and no annotations, the description is incomplete for safe and correct usage.

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% with descriptions for all four parameters. The tool description adds no additional meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (add) and resource (new stage to existing pipeline). It distinguishes from siblings like rename_pipeline_stage, but does not explicitly differentiate from get_pipeline_statuses or other modification tools.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as rename_pipeline_stage or when to check pipeline existence. The description does not mention prerequisites or context for correct invocation.

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