Skip to main content
Glama
paskal

bitrix24-mcp-server

by paskal

bitrix24_crm_deal_list

List and filter CRM deals from Bitrix24 using flexible criteria. Support sorting, pagination, and selecting specific fields to retrieve targeted deal data.

Instructions

List and filter CRM deals

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax deals to return. WITHOUT this the tool returns at most 500 (10 pages x 50) and silently truncates — the response 'total' shows the true match count while 'deals' is capped at 500. For a query that matches more, pass limit >= total to fetch everything.
orderNoSort order, e.g. {ID: 'desc'}
filterNoFilter, e.g. {STAGE_ID: 'WON', 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
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. The description text 'List and filter CRM deals' reveals nothing about truncation, pagination, or operator reliability, which are critical for correct invocation.

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

Conciseness3/5

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

The description is extremely concise (5 words), but it provides only a basic purpose. It lacks structural elements like bullet points or contextual cues expected for a tool with 4 parameters.

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?

Given the tool's complexity (4 parameters, nested objects, no output schema), the one-line description is insufficient. Important details about return behavior and filtering are omitted from the description itself.

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 coverage is 100%, so baseline is 3. The description adds no parameter meaning beyond the schema, but the schema's parameter descriptions are detailed. The description itself does not enhance semantics.

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 deals' clearly states the verb (list and filter) and the resource (CRM deals), differentiating it from sibling tools like bitrix24_crm_deal_get which retrieves a single deal.

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 provides no explicit guidance on when to use this tool versus alternatives (e.g., bitrix24_crm_deal_get for single deals). Usage context is implied but not stated.

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/paskal/bitrix24-mcp-server'

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