Skip to main content
Glama
paskal

bitrix24-mcp-server

by paskal

bitrix24_call_transcribe

Transcribe Bitrix24 CRM call recordings locally and offline using Whisper large-v3. Provide a call activity ID to receive the transcript text, segments, manager ID, and call direction without any data leaving your machine.

Instructions

Transcribe a CRM call recording LOCALLY and fully offline (audio never leaves the machine). Resolves the call's recording (Voximplant/Mango RECORD_FILE_ID), downloads it, and decodes it with local Whisper large-v3 (strong Russian). Works out of the box — the MCP auto-bootstraps its own Python venv + model on first use (first call is slow: it downloads the ~3 GB model). A bounded worker pool serves calls, so firing hundreds at once just queues and drains N-at-a-time. This does NOT write anything to Bitrix — it only returns the transcript. To store it, the caller saves it with bitrix24_crm_timeline_note_save. Returns {text, segments, responsibleId, direction}: raw, unlabelled segments (Whisper splits by pause, not by speaker). For «who-said-what» labels the calling model decides — it has responsibleId (the manager) here and the client's name on the lead. Substitutes for Bitrix's UI-only call transcription/BitrixGPT scoring, which is NOT in the REST API. NOTE: phone audio is 8 kHz mono (mixed-speaker), so expect substance-accurate but imperfect text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activityIdYesThe call activity ID (from bitrix24_crm_activity_list — a VOXIMPLANT_CALL activity)
Behavior5/5

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

With no annotations, the description fully covers behavioral traits: offline processing, model download on first use, bounded worker pool, no writes to Bitrix, raw segments without speaker labels, audio quality caveats, and return structure. No contradictions.

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?

Description is efficiently structured: purpose in first sentence, key details following. Every sentence adds value (e.g., model download, worker pool, no write, return format, audio quality). No waste.

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?

Covers all necessary aspects for an agent: how it works, prerequisites, return format, limitations (no speaker labels, audio quality), and links to saving alternative. No output schema, but description compensates.

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?

Single parameter 'activityId' has 100% schema coverage with clear description. The tool description adds no additional parameter details beyond what the schema provides, meeting baseline but not exceeding.

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 tool transcribes CRM call recordings locally and offline, using specific verb 'Transcribe' and resource 'CRM call recording'. It distinguishes from siblings by emphasizing 'LOCALLY and fully offline' and mentions that it substitutes for Bitrix's UI-only transcription not available via REST API.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides guidance on when to use (local transcription), notes first-call slowness due to model download, describes queue behavior for multiple calls, and explicitly states that the tool does NOT write to Bitrix (for saving, use alternative sibling tool). However, it does not compare with the sibling tools 'transcribe_fast' or 'transcribe_max'.

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