Skip to main content
Glama
wdavidce

Kommo MCP Server

by wdavidce

create_lead_complex

Create a lead and link it to a contact in Kommo, automatically searching for existing contacts by phone, CPF, email, or name. If found, update the contact and lead instead of duplicating.

Instructions

Creates a new lead and links it to a new contact in Kommo in a single request. BUT BEFORE CREATING: it will automatically attempt to search for the contact using the provided 'phone', 'cpf', 'email' or 'contact_name'. If a contact already exists, it will UPDATE the contact and its lead instead. Automatically maps custom field NAMES to their IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lead_nameNoLead Name
priceNoLead price/value (MUST BE AN INTEGER no decimals. e.g. 150.50 -> 150)
pipeline_idNoPipeline ID
status_idNoStatus ID inside the pipeline
lead_custom_fieldsNoKey-value pairs of LEAD custom fields (keys are exact field NAMES).
contact_nameNoContact Name
contact_custom_fieldsNoKey-value pairs of CONTACT custom fields (keys are exact field NAMES).
Behavior4/5

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

Discloses key behaviors: automatic contact search via specified fields, conditional update instead of creation, and automatic mapping of custom field names to IDs. No annotations exist, so description carries full burden; it is mostly adequate but omits potential error cases.

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 concise sentences front-loaded with core purpose, followed by critical exceptions and automation details. No wasted words.

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

Completeness3/5

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

Description covers behavior and custom field mapping but lacks output information, required parameter indication (all optional), and error scenarios. Given complexity and no output schema, more detail expected.

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% and description adds marginal value beyond schema (only price integer constraint). The behavioral context (auto-search, field mapping) is helpful but does not elaborate on individual parameter semantics beyond what is in 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?

Description clearly states it creates a lead and links it to a contact in a single request, distinguishing it from sibling tools like update_lead or search_contacts. The verb 'creates' and resource 'lead+contact' are specific.

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?

Explicitly describes automatic search and update behavior before creation, guiding when to use this tool for upserting. However, it does not explicitly contrast with sibling tools like update_lead or create_lead (if existed).

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/wdavidce/kommo-mcp-server'

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