Skip to main content
Glama
kylastech

Kylas CRM MCP Server

Official
by kylastech

lookup_users

Search for CRM users by name or list all users. Use return_all to fetch complete user list in one response.

Instructions

Look up users by name, or list all users in the system.

  • Use return_all=True (with query "name:" or empty) to fetch all users in one response (all pages combined).

  • For name search: query in field:value form (e.g. "firstName:last", "name:Last"). If one user is found, use that ID in search_leads; if multiple, ask which one. query: Search string (e.g. "firstName:last", "name:Last"). Use "name:" or leave default to list all when return_all=True. page: 0-based page (default 0). Ignored when return_all=True. size: Page size, max 50 (default 50). Used per page when return_all=True. return_all: If True, fetch all pages and return every user in one response (cap 500).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoname:
pageNo
sizeNo
return_allNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses pagination behavior, cap of 500 for return_all, and parameter interactions. Could mention error conditions or rate limits, but still strong.

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?

Concise with no wasted words. Front-loaded purpose, then bullet-point parameter details. Two sentences cover behavior and cross-reference.

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 complexity and existence of an output schema, the description fully covers input behavior, pagination, limits, and cross-tool usage. No gaps.

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?

Schema coverage is 0%, so description must compensate. It explains each parameter: query format (e.g., 'firstName:last'), page as 0-based, size max 50, return_all behavior. Adds significant value beyond 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?

The description clearly states 'Look up users by name, or list all users in the system.' This is a specific verb and resource, and it distinguishes this tool from siblings which deal with leads, pipelines, etc.

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?

Provides explicit guidance on when to use return_all=True, how to format the query, and even cross-references search_leads for the user ID. This helps the agent decide when to use this tool vs alternatives.

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