Skip to main content
Glama
depper-IA

Kommo Kiro MCP

by depper-IA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_lead

Add a new lead (deal) to Kommo CRM with a title, price, stage, pipeline, and tags. Missing tags are created automatically; each call makes a new lead.

Instructions

Create one lead in Kommo. Not idempotent: each call creates a new lead. Tag names that do not exist yet are created automatically. Returns the created lead object. To create the contact and company in the same call, use create_lead_complex.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesLead name (title of the deal).
tagsNoTag names to attach, e.g. ["vip", "web"]. Created if missing.
priceNoDeal value in the account currency, e.g. 1500.
stage_idNoStage (status) to place the lead in. Get IDs from list_stages. Omit for the first stage of the pipeline.
pipeline_idNoPipeline to create the lead in. Get IDs from list_pipelines. Omit to use the account default.
responsible_user_idNoKommo user ID to assign as owner. Omit for the default user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Lead name"New value: +"Lead name (title of the deal)."
    • changedInput schema / properties / pipeline_id / description
      Previous value: -"Target pipeline ID"New value: +"Pipeline to create the lead in. Get IDs from list_pipelines. Omit to use the account default."
    • changedInput schema / properties / price / description
      Previous value: -"Deal value"New value: +"Deal value in the account currency, e.g. 1500."
    • changedInput schema / properties / responsible_user_id / description
      Previous value: -"Assigned user ID"New value: +"Kommo user ID to assign as owner. Omit for the default user."
    • changedInput schema / properties / stage_id / description
      Previous value: -"Target stage ID"New value: +"Stage (status) to place the lead in. Get IDs from list_stages. Omit for the first stage of the pipeline."
    • changedInput schema / properties / tags / description
      Previous value: -"Tag names"New value: +"Tag names to attach, e.g. [\"vip\", \"web\"]. Created if missing."
  2. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare idempotentHint=false, readOnlyHint=false and openWorldHint=true, so the description need not restate the safety profile. It still adds real context beyond the structured data: non-idempotency restated in plain terms, automatic tag creation as a side effect, and the return value despite no output schema.

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, each carrying distinct information: creation semantics, idempotency, tag side effect, return value, and sibling routing. Front-loaded with the core purpose and no filler.

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?

Although no output schema exists, the description states that the created lead object is returned, and it covers the notable side effect (auto-created tags). For a single-entity create tool with full schema coverage, nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, so every parameter (including stage_id, pipeline_id and responsible_user_id) is already documented in the schema. The description only adds the tag auto-creation behavior, which is a side effect rather than parameter meaning. Baseline 3 applies.

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 ('Create one lead in Kommo') with the scope-limited singular cardinality, and explicitly distinguishes itself from create_lead_complex. An agent can tell it apart from the bulk/complex siblings without opening a 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?

Names the alternative create_lead_complex and the exact condition that selects it (when contact and company must be created in the same call). It stops short of stating exclusions such as when to prefer bulk operations, but the routing guidance is clear.

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

Deploy Server

Other Tools