Skip to main content
Glama
paskal

bitrix24-mcp-server

by paskal

bitrix24_im_message_send

Send a new IM message to a Bitrix24 user or group chat using BBCode formatting for bold, italic, and links.

Instructions

Send a NEW Bitrix24 IM message. Use this to message a person privately (1-on-1) or post into a group/task chat — it's the send counterpart to bitrix24_im_message_update (edit) and bitrix24_im_message_delete. The message is sent under the webhook owner's identity. For a PRIVATE 1-on-1 message pass the recipient's numeric user ID as dialogId (e.g. '8' for Aleksandr); for a group/task chat pass 'chatNNN'. Returns the new message ID (reuse it with update/delete). FORMATTING — plain text + BBCode only; Bitrix does NOT parse Markdown (bold, backticks, # headings render literally). Supported: [B]bold[/B], [I]italic[/I], [U]under[/U], [S]strike[/S], [URL=...]text[/URL], [USER=ID]Name[/USER] mentions. For bullet lists put a literal • at the line start — []/[LIST] do NOT render in chat (they show as literal «[]»); no tag exists for inline code/filename, wrap in «…». When attaching a file to a chat (the disk im.disk.file.commit MESSAGE caption), keep the caption to ONE short line and post any long explanation as a SEPARATE following message — captions render in an oversized font, so a multi-paragraph caption becomes a wall of text. To post a comment onto a TASK specifically, prefer bitrix24_task_comment_add (it also shows in the task comment section). DISCLOSURE — the message text MUST end with a final line, on its own, reading exactly «(написано агентом)»: it posts under the human owner's account but is agent-written, and this line discloses that to the reader (owner rule, favor-group).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesMessage text — plain text + BBCode only, NO Markdown. Bullet lines start with • (not [*]). See tool description for the full formatting contract + the file-caption rule.
dialogIdYesRecipient: numeric user ID as a string for a private 1-on-1 message (e.g. '6'), or 'chatNNN' for a group/task chat
Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: the message is sent under the webhook owner's identity, returns the new message ID, the formatting limitations (BBCode only, no Markdown, specific tags), the file caption rule, and the mandatory disclosure line. This is comprehensive 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 relatively long but well-structured, starting with purpose and sibling relationships, then parameter details, formatting rules, and special cases. Every sentence earns its place, though it could be slightly more concise by grouping related information more tightly.

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?

Given no annotations, no output schema, and a complex tool with formatting and behavior nuances, the description is complete: it covers invocation, formatting, disclosure, file attachment behavior, and alternatives. There is little ambiguity left for the agent.

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

Parameters5/5

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

Schema coverage is 100%, so baseline is 3, but the description adds significant value: it explains dialogId format with concrete examples (e.g., '8' for Aleksandr, 'chatNNN'), details the text formatting contract (BBCode support, bullet list syntax, disclosure line), and adds the file-caption rule not found in the schema.

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 ('Send a NEW Bitrix24 IM message') and specifies the resource (private 1-on-1 or group/task chat). It explicitly distinguishes from sibling tools by naming bitrix24_im_message_update, bitrix24_im_message_delete, and bitrix24_task_comment_add, making the purpose unambiguous.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use scenarios (private message vs. group chat) and when-not-to-use (task comments should use bitrix24_task_comment_add). It also includes detailed formatting rules and a disclosure requirement, giving clear guidance on correct invocation.

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