Skip to main content
Glama
kylastech

Kylas CRM MCP Server

Official
by kylastech

search_leads

Search and filter leads using customizable criteria like name, country, source, and date. Specify fields, operators, and values to find specific leads in Kylas CRM.

Instructions

Search/filter leads. Only fields marked [FILTERABLE] in get_lead_field_instructions can be used. Call get_lead_field_instructions first to get filterable fields and their types.

filters: List of filter objects. Each must have:

  • field (str): Field internal/API name (e.g. firstName, country, source, createdAt).

  • operator (str): One of the allowed operators for that field type (e.g. equal, contains, greater).

  • value: Value to compare. For PICK_LIST/MULTI_PICKLIST use Option ID (number), except requirementCurrency, companyBusinessType, country, timezone, companyIndustry — use internal name (string). For date/datetime (incl. custom e.g. cfDateField): value null for today/is_null/is_not_null; single ISO string for greater/greater_or_equal/less/less_or_equal e.g. "2026-02-02T18:30:00.000Z"; for between use [startISO, endISO].

  • timeZone (str, optional): For date/datetime filters only; default from server or env.

  • type (str, optional): Field type from cheat sheet. If omitted, inferred from schema. For user look-up fields (createdBy, updatedBy, convertedBy, ownerId, importedBy): value must be user ID (number). Call lookup_users first. For the products field: value must be product ID (number). Call lookup_products first; if multiple matches, ask which product, then use that ID here. For pipeline / pipelineStage (e.g. open leads, closed leads): call lookup_pipelines first, ask the user to confirm which pipeline, then call get_pipeline_stages for that pipeline only; if stage is ambiguous ask which stage, then use pipeline + pipelineStage filters here. page: 0-based page (default 0). size: Page size, max 100 (default 20). sort: Sort e.g. "createdAt,desc" (default).

Operators by type (examples): TEXT_FIELD: equal, contains, is_empty. NUMBER: equal, greater, between, is_null. PICK_LIST: equal, in, is_null. DATETIME_PICKER: today, yesterday, between, is_not_null, greater, less, current_week, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filtersYes
pageNo
sizeNo
sortNocreatedAt,desc

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does not explicitly state that the operation is read-only, but it is implied by 'search'. The description does not disclose potential side effects, rate limits, or response size constraints. It does, however, thoroughly explain the filter constraints and special cases, which adds some transparency but omits behavioral aspects like data freshness or timeout behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is lengthy but well-structured with clear sections and examples. It is front-loaded with the main purpose and prerequisites. While some repetition exists (e.g., multiple 'call...first' patterns), the complexity of the tool justifies the length. The bullet-point formatting aids readability.

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?

Given the tool's complexity (4 parameters, nested filter objects, high parameter logic), the description is extremely comprehensive. It covers all filtering variations, special handling for different field types, and pagination. No critical input aspect is missing. Since an output schema exists, the description does not need to explain return values. The description fully contextualizes the tool's usage.

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

Parameters5/5

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

The input schema has 0% description coverage, so the description must compensate entirely. It does so excellently by explaining each parameter in depth: the filters array structure, field types, operators, special cases for dates, picklists, user lookups, products, and pipelines. It also covers pagination and sorting defaults. This goes far beyond what the schema provides, enabling the agent to use the tool correctly.

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 tool's purpose: 'Search/filter leads.' However, it does not distinguish this tool from sibling tools like search_leads_by_term or search_idle_leads, which are likely more specialized. The lack of differentiation prevents the agent from knowing when to use this tool over alternatives.

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 detailed step-by-step instructions for constructing filters (e.g., calling get_lead_field_instructions first, special handling for user lookups, pipelines, etc.), but it offers no guidance on when to use this tool vs. other search tools. There is no mention of scenarios where this tool is appropriate or inappropriate compared to alternatives, leaving the agent without comparative context.

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/kylastech/kylas-crm-mcp-server'

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