Skip to main content
Glama
depper-IA

Kommo Kiro MCP

by depper-IA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_lead_complex

Create a lead together with a new contact, company, tags, stage, and pipeline in one request. Use it when records must be created together; it always creates new records, not links existing ones.

Instructions

Create a lead together with a new contact and/or company in one request (POST /leads/complex). Not idempotent: always creates new records, never links existing ones. Returns the created lead. Phone and email are stored only if the account has contact fields named or coded PHONE and EMAIL. Use create_lead if no contact or company is needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesLead name (title of the deal).
tagsNoTag names to attach to the lead. Created if missing.
stage_idNoStage for the lead. Get IDs from list_stages.
pipeline_idNoPipeline for the lead. Get IDs from list_pipelines.
company_nameNoName of a new company to create and attach.
contact_nameNoName of a new contact to create. Phone and email are ignored unless this is set.
contact_emailNoContact email address.
contact_phoneNoContact phone number, e.g. +15551234567.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / company_name / description
      Previous value: -"Company name"New value: +"Name of a new company to create and attach."
    • changedInput schema / properties / contact_email / description
      Previous value: -"Contact email"New value: +"Contact email address."
    • changedInput schema / properties / contact_name / description
      Previous value: -"Contact full name"New value: +"Name of a new contact to create. Phone and email are ignored unless this is set."
    • changedInput schema / properties / contact_phone / description
      Previous value: -"Contact phone number"New value: +"Contact phone number, e.g. +15551234567."
    • changedInput schema / properties / name / description
      Previous value: -"Lead name"New value: +"Lead name (title of the deal)."
    • addedInput schema / properties / pipeline_id / description
      Added value: +"Pipeline for the lead. Get IDs from list_pipelines."
    • addedInput schema / properties / stage_id / description
      Added value: +"Stage for the lead. Get IDs from list_stages."
    • addedInput schema / properties / tags / description
      Added value: +"Tag names to attach to the lead. Created if missing."
  2. First observedv1.0.0

TDQS

A4.7/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, but the description goes further by explaining what that means (always creates new records, never links existing ones) and adds a non-obvious conditional: phone/email are only stored if the account has PHONE/EMAIL contact fields. It does not mention auth/permission requirements or error behavior, so not a full 5.

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, front-loaded with what it does and the endpoint, followed by the most actionable caveat (non-idempotency) and the alternative. No redundancy or 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?

For an 8-parameter creation tool with no output schema, the description covers what it returns ('Returns the created lead'), the non-idempotent nature, the composite-creation semantics, and the fallback tool. Nothing an agent needs before calling is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: the account-level PHONE/EMAIL field prerequisite constrains when contact_phone/contact_email take effect, and the 'in one request' framing clarifies that company_name/contact_name create new records.

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+resource ('Create a lead together with a new contact and/or company in one request') and even names the endpoint POST /leads/complex. It is immediately distinguishable from the sibling create_lead because it explicitly scopes the composite behavior.

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

Usage Guidelines5/5

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

Gives an explicit routing rule: 'Use create_lead if no contact or company is needed.' It also warns 'Not idempotent: always creates new records, never links existing ones,' telling the agent when this tool is the wrong choice for linking to existing contacts/companies.

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