Skip to main content
Glama
Sign In
bitrix24-mcp-server

bitrix24-mcp-server

by paskal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bitrix24_user_search

Search for users in Bitrix24 by name, email, or other query to locate contact information.

Instructions

Search Bitrix24 users by name

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "bitrix24_user_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query (name, email, etc.)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It does not state whether the operation is read-only or has side effects, nor does it mention authentication or rate limits. The description says 'by name' but the schema parameter accepts 'name, email, etc.', causing a slight inconsistency.

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 a single concise sentence, but it could afford to be slightly more informative without losing conciseness. It is front-loaded and efficient.

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?

With no output schema, the description should explain return values or pagination. It does not mention what the tool returns (list of users, IDs, details), nor any limitations or common use cases, leaving the agent underinformed.

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

Parameters2/5

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

Schema coverage is 100%, so baseline is 3. However, the description adds minimal value beyond the schema; it only refines the search to 'by name' while the schema already includes broader options. No additional parameter details are provided.

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 the verb 'Search', resource 'Bitrix24 users', and criterion 'by name'. It distinguishes itself from sibling tools like bitrix24_user_get (single user retrieval) and bitrix24_im_chat_search (chat search).

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?

No guidance on when to use this tool vs alternatives. Does not mention that for a specific user ID one should use bitrix24_user_get, or that the query supports email and other fields beyond name.

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