Skip to main content
Glama

b24_calendar_event_add

Creates a calendar event in Bitrix24 with title, start and end times, and optional details like attendees or location. Returns the new event ID.

Instructions

Create a calendar event (calendar.event.add). Returns the new event id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesEvent title.
extraNoAny additional calendar.event.add fields (e.g. {'description':'...','attendees':[1,2],'location':'...'}).
date_toYesEnd, 'YYYY-MM-DD HH:MM:SS'.
owner_idNoCalendar owner id. Defaults to the acting user (resolved via user.current) for owner_type='user'.
date_fromYesStart, 'YYYY-MM-DD HH:MM:SS'.
owner_typeNoCalendar owner type: 'user' (default) or 'group'.user
section_idNoTarget calendar (section) id. If omitted Bitrix uses the owner's default calendar.
webhook_urlNoOverride the default incoming webhook for this call (https://<portal>/rest/<user_id>/<token>/). If omitted, uses personal_webhook, then the X-B24-Webhook HTTP header, then the BITRIX_WEBHOOK_URL env default.
personal_webhookNoAct as a specific user (their personal incoming webhook). Takes precedence over webhook_url. Required to write to the portal under that user's permissions.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare this as a non-read-only, non-destructive mutation. The description adds that it returns the new event ID, but lacks details on side effects, permission requirements, or error conditions.

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?

The description is a single, front-loaded sentence that efficiently states purpose and return value. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite many parameters and siblings, the description is minimal. It does not cover return format beyond 'new event id', error handling, or how to leverage the 'extra' parameter effectively. Output schema exists but is not described.

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?

All parameters have schema descriptions, so the tool description adds no additional meaning. The 'extra' parameter allows open-world additions, but the description merely restates 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 'Create' and the resource 'calendar event', and mentions the return value. It distinguishes itself from sibling tools like delete or list by specifying the action.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., b24_task_add, b24_crm_activity_add). No exclusions, prerequisites, or context provided.

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/john7ross/BitrixMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server