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

bitrix24-mcp-server

by paskal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bitrix24_crm_contact_list

Retrieve and filter your Bitrix24 CRM contacts with sorting, field selection, and flexible filter options including date and ID comparisons.

Instructions

List and filter CRM contacts

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bitrix24_crm_contact_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax contacts to return
orderNoSort order, e.g. {ID: 'desc'}
filterNoFilter, e.g. {ASSIGNED_BY_ID: 854}. Comparison operators DO work here, re-verified against this portal 2026-07-28: {'>=DATE_CREATE': '2026-07-20T00:00:00+03:00'} (inclusive, full ISO timestamp honoured), {'>DATE_CREATE': ...} (exclusive), {'>=ID': N} and {'>ID': N} all filter correctly — this tool posts the filter as JSON, so the curl --data-urlencode trap (which leaves the '>' in the KEY unencoded and makes Bitrix drop the condition) does not apply. Date-only values with a strict '>' are NOT required. The operator that IS unreliable: {FIELD: ''} ("is empty") on UF string fields returns records regardless (measured: 8 of 50 rows came back non-empty), so always client-check the value. {'!FIELD': ''} (truthy) and {FIELD: value} (exact) are reliable.
selectNoFields to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'List and filter', failing to mention default behavior, pagination, sort order, or side effects. The detailed filter operator notes are in the schema, not the description, so the description itself offers minimal transparency.

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 concise (4 words) and front-loaded with the action. It is efficient with no fluff, but it omits important context that could justify a slightly longer description. Still, it earns a 4 for being to the point.

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?

For a list tool with no output schema, the description should disclose what is returned (e.g., array of contacts), default ordering, pagination limits, etc. It fails to provide this, leaving the agent with insufficient context to understand the tool's full behavior.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond 'List and filter'—it does not elaborate on parameters or their usage beyond what the schema already provides.

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 'List and filter CRM contacts' clearly specifies the verb (list and filter) and resource (CRM contacts). It effectively distinguishes this tool from sibling tools like bitrix24_crm_contact_get (single contact) and bitrix24_crm_deal_list (deals).

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?

The description implies usage when listing or filtering contacts but provides no explicit guidance on when to use this tool versus alternatives (e.g., get for single contacts) or any exclusions. No context about appropriate scenarios is given.

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