Skip to main content
Glama
E0DUAR

Kommo CRM MCP Server

by E0DUAR

kommo_update_lead

Updates an existing lead in Kommo CRM by modifying its name, price, status, or pipeline.

Instructions

Update an existing lead

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
leadIdYes
nameNo
priceNo
status_idNo
pipeline_idNo
Behavior1/5

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

With no annotations, the description must disclose behavioral traits like side effects or auth needs. It only says 'update an existing lead', providing no transparency.

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

Conciseness2/5

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

The description is a single short sentence, which is concise but under-informative; it sacrifices completeness for brevity.

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

Completeness1/5

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

Without annotations, output schema, or parameter explanations, the description is insufficient for an agent to understand tool behavior and usage, especially given 5 parameters and many sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain any parameters (e.g., what status_id or pipeline_id represent). Fails to add value beyond 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?

The description 'Update an existing lead' clearly states the verb and resource, distinguishing it from creation tools and other update tools like kommo_update_lead_custom_fields.

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 kommo_update_lead_custom_fields or when not to use it. Missing context about prerequisites or typical use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/E0DUAR/kommo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server