Skip to main content
Glama
Miguelgbastos

Kommo CRM MCP Server

move_lead_to_status

Move a lead to a specified status in Kommo CRM by providing the lead ID and target status ID, enabling precise workflow and pipeline management.

Instructions

Move a lead to a specific status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lead_idYesID of the lead
status_idYesID of the target status

Implementation Reference

  • This is the core handler function that implements the logic to move a lead to a specific status in Kommo CRM by sending a PATCH request to update the status_id of the lead.
    async moveLeadToStatus(leadId: number, statusId: number): Promise<KommoLead> {
      const response = await this.client.patch(`/api/v4/leads/${leadId}`, { status_id: statusId });
      return response.data;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Move' implies a state change operation, but the description doesn't disclose whether this requires specific permissions, whether the operation is reversible, what happens to the lead's previous status, or any rate limits. For a mutation tool with zero annotation coverage, this is inadequate.

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?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized for a simple operation and front-loads the essential information immediately.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens during the move operation, what the response looks like, or any side effects. Given the complexity of state transitions and the lack of structured safety information, more context is needed.

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 both parameters are documented in the schema. The description doesn't add any meaningful parameter semantics beyond what the schema already provides (lead_id and status_id). The baseline score of 3 is appropriate when the schema does the heavy lifting.

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 ('move') and resource ('lead to a specific status'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'move_lead_to_pipeline' or 'create_lead_status', but the verb+resource combination is specific enough for basic understanding.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when not to use it, or how it differs from sibling tools like 'move_lead_to_pipeline' or 'create_lead_status' that also manipulate lead states.

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

Related 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/Miguelgbastos/Kommo-MCP'

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