MCP server for integrating with Bitrix24 CRM, enabling lead management operations
Two tools with basic schemas and minimal descriptions. get_leads lacks parameter detail (filter is untyped object with no constraints); create_lead has required title but missing status enum. Descriptions are generic (10-30 chars) and do not explain WHEN to use each tool or what the LLM should expect. No output schema documented. Error handling is present but generic ('Failed to fetch leads'). No pagination support despite list operation. No tool annotations (readOnlyHint/destructiveHint). Naming is acceptable (verb_noun) but descriptions fall well below the 50-200 char baseline for A+ tools.
Create a new lead in Bitrix24
Fetch leads from Bitrix24
Descriptions are too short (10-30 chars) and lack context. 'Fetch leads from Bitrix24' does not explain when to use this vs other discovery tools, what fields are returned, or pagination behavior. Baseline for A+ tools is 50-200 chars.
get_leads filter parameter is an untyped object with no constraints, examples, or nested field documentation. LLMs cannot infer valid filter keys (e.g., NAME, EMAIL, PHONE, STATUS). Should document expected filter structure or provide enum examples.
create_lead status parameter lacks enum constraint. Description says 'Lead status' but does not list valid values (e.g., NEW, IN_PROGRESS, CONVERTED, LOST). LLMs will hallucinate invalid status values.
No output schema documented for either tool. get_leads returns {leads: [...]} but structure of each lead object is not specified. create_lead returns {leadId: ...} but type and format are unclear. LLMs cannot plan downstream calls without knowing response structure.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 39 | 2026-07-28+ | v2 |
get_leads has no pagination support (limit, offset, page_size). Bitrix24 API likely returns many leads; unbounded results will exhaust context window. Should accept limit (default 20, max 100) and offset/cursor parameters.