Skip to main content
Glama
depper-IA

Kommo Kiro MCP

by depper-IA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_custom_field

Creates a custom field on Kommo leads, contacts, or companies for storing extra CRM data. Provide entity type, field type, and name; check existing fields first to avoid duplicates.

Instructions

Create a custom field on leads, contacts, or companies. Not idempotent: each call creates another field, so check list_custom_fields first. Returns the created field. Clears the custom-field cache for that entity. Provide enum_values for select-type fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesField display name.
field_typeYesKommo field type sent as-is, e.g. text, numeric, select, multiselect, date, url, checkbox.
entity_typeYesEntity to add the field to: leads, contacts, or companies.
enum_valuesNoOption labels for select or multiselect fields, in display order, e.g. ["Low", "High"]. Ignored by other types.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / entity_type / description
      Previous value: -"leads, contacts, or companies"New value: +"Entity to add the field to: leads, contacts, or companies."
    • changedInput schema / properties / enum_values / description
      Previous value: -"Values for select/multiselect fields"New value: +"Option labels for select or multiselect fields, in display order, e.g. [\"Low\", \"High\"]. Ignored by other types."
    • changedInput schema / properties / field_type / description
      Previous value: -"text, numeric, select, multiselect, date, url, checkbox"New value: +"Kommo field type sent as-is, e.g. text, numeric, select, multiselect, date, url, checkbox."
    • changedInput schema / properties / name / description
      Previous value: -"Field name"New value: +"Field display name."
  2. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Adds real behavioral context beyond the annotations: the non-idempotency consequence ('each call creates another field'), the cache-clearing side effect ('Clears the custom-field cache for that entity'), and the return value. The cache side effect is not derivable from annotations and is exactly the kind of mutation disclosure an agent needs.

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 tight sentences, each carrying distinct information (purpose, non-idempotency warning, return, cache effect, param guidance), with the core action front-loaded. 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?

For a mutation tool with no output schema, the description covers the return value, the idempotency hazard, and a side effect, and the schema fully documents all four parameters. Nothing an agent needs to call this correctly 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 actionable semantics by tying enum_values to select-type fields in a usage instruction. It doesn't explain field_type values beyond what the schema already documents, keeping it slightly above baseline rather than maximal.

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 custom field') and enumerates the target scope (leads, contacts, or companies), which lets an agent distinguish it from read-oriented siblings like list_custom_fields at a glance.

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?

Explicitly names the alternative ('check list_custom_fields first') and gives a conditional usage rule ('Provide enum_values for select-type fields'). Both the when-to-use and the prerequisite are stated, not inferred.

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