Skip to main content
Glama
paskal

bitrix24-mcp-server

by paskal

bitrix24_crm_timeline_note_save

Save a note to a CRM timeline item (e.g., a call). Modes: create (no overwrite if note exists), replace, or append.

Instructions

Save the «заметка» note on a CRM timeline item (e.g. the note on a specific call, so it appears at the call, not as a loose lead comment). A timeline item has exactly ONE note — saving REPLACES it. Anti-clobber safeguard: in the default mode='create', if a note already exists this does NOT overwrite it — it writes your text to a local draft file and returns the existing note plus a recommendation, so the calling model can decide. Re-call with mode='replace' to overwrite, or mode='append' to keep both (existing + a separator + new).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNocreate (default): save only if no note exists; if one exists, do NOT overwrite — return it + a draft file so you can decide. replace: overwrite any existing note. append: existing note + separator + new text.
textYesNote text to save
itemIdYesTimeline item ID — for a call note this is the call activity's ID
ownerIdYesID of the lead/deal/contact/company
itemTypeNoTimeline item type the note hangs off (default 'activity')
ownerTypeYesCRM entity the timeline item belongs to
Behavior5/5

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

No annotations are provided, so the description fully covers behavioral traits: note replacement, mode-specific behaviors (draft file, return of existing note in create mode), and the exact effects of each mode.

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 a single paragraph, efficiently covering purpose and all modes without redundancy. It could use slight structuring but is effective.

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 the complexity (three modes, 6 parameters), the description explains all relevant details: the one-note constraint, mode behaviors, and parameter context. No output schema needed; return values are hinted.

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

Parameters4/5

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

Schema has 100% description coverage, but the tool description adds significant context beyond schema (e.g., 'for a call note this is the call activity's ID' for itemId, and mode behavior details). It adds value.

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 'save' and the resource 'note on a CRM timeline item', with a specific example of call notes. It distinguishes from generic note saving by specifying the timeline context.

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?

The description provides explicit guidance on the three modes (create, replace, append) and their effects, including the anti-clobber safeguard. It lacks direct comparison to sibling note retrieval tool but is otherwise clear.

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