Skip to main content
Glama
paskal

bitrix24-mcp-server

by paskal

bitrix24_task_post_image

Post images as inline thumbnails in Bitrix24 task chat messages. Each image file gets its own message with the same caption, ensuring inline display without clicking.

Instructions

Post chat message(s) to a Bitrix24 task with images that render INLINE as thumbnails (not just filename links). Use this for screenshots, design mockups, photo evidence — anything where the reader should see the image without clicking through. Each local file path is uploaded to disk, then a SEPARATE chat message is posted per image (Bitrix renders multi-image single-messages with broken second-image placeholders — verified 2026-05-19). The same message caption is reused on each image's message; if you want per-image captions, call this tool once per image with a distinct message. Returns array of IM message IDs (one per image). Files are saved to B24 disk (folder 732896 by default) so they're permanently accessible, but NOT added to UF_TASK_WEBDAV_FILES — for that, use bitrix24_task_attach_file separately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesTask ID to post into
messageYesCaption posted above each image. Same text on every message. Supports BBCode ([B]…[/B], [URL=…]…[/URL], [USER=ID]Name[/USER]). For distinct per-image captions, call this tool multiple times with single-element filePaths arrays.
folderIdNoDisk folder ID for upload. Default 732896 (shared 'Блог' folder, verified writable for user 854).
filePathsYesArray of absolute local paths to image files (PNG / JPG / WebP). One message posted per file.
Behavior5/5

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

Discloses that images render inline, each image gets a separate message due to a verified bug, files saved to disk folder 732896, permanently accessible but not added to task file field. Returns array of message IDs.

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?

Description is long but every sentence serves a purpose. Front-loads key features and differentiators. Could be slightly more concise but still efficient.

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 complexity (4 params, no output schema, platform bug), description covers all needed context: return format, caveats, sibling tool relationship, and default behavior.

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?

Adds rich context beyond schema: explains separate message behavior per file, default folder verification, BBCode support, and per-image caption strategy. All parameters are well described.

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 posts chat messages with inline image thumbnails, distinguishes from bitrix24_task_attach_file, and notes that files are not attached to task file field.

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?

Explicitly recommends use for screenshots, design mockups, photo evidence. Tells when not to use (for attaching to UF_TASK_WEBDAV_FILES) and points to sibling bitrix24_task_attach_file. Advises on per-image captions.

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