Skip to main content
Glama

kommo_search_leads

Search leads in a CRM using filters for text, pipeline, stage, and responsible user. Returns leads with embedded contact details.

Instructions

Busca leads. Filtra por texto (query), funil, etapa e responsável. Retorna leads com contatos embutidos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
limitNo
queryNoTexto livre (nome, telefone, etc.)
status_idNo
pipeline_idNo
responsible_user_idNo
Behavior2/5

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

No annotations provided. Description only mentions return of leads with contacts, but lacks details on pagination (page/limit), search behavior (exact/partial match), or rate limits. More transparency needed.

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?

Two concise sentences, front-loaded with action and filters. No redundant information.

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?

Missing explanation of pagination behavior and how to handle results beyond 'retorna leads com contatos embutidos'. No output schema, so more detail on return structure would be helpful.

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?

Adds meaning for 4 of 6 parameters: query (texto libre), pipeline_id (funil), status_id (etapa), responsible_user_id (responsável). Does not cover page and limit, but schema has defaults and max. With low schema coverage (17%), description compensates for most parameters.

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 'Busca leads' and lists filtering criteria (query, funnel, stage, responsible). It distinguishes from sibling tools like kommo_get_lead (single lead) and kommo_search_contacts (contacts).

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

Usage Guidelines3/5

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

Implies usage for searching leads with filters, but no explicit when-to-use or when-not-to-use guidance. Does not mention alternatives among siblings.

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

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