Bitrix24 MCP server

b24_calendar_list

Retrieve calendar events filtered by date for personal, group, or company calendars.

Instructions

Lista eventos de calendario personal, de grupo o de empresa con filtro de fechas.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "b24_calendar_list"
  }
}

Input Schema

Name	Required	Description	Default
`type`	No	Tipo de calendario: user (personal), group (grupo de trabajo), company_calendar (empresa)	user
`owner_id`	No	ID del usuario o grupo propietario. Default: usuario del webhook
`from`	No	Fecha inicio ISO8601. Ejemplo: "2026-01-01"
`to`	No	Fecha fin ISO8601. Ejemplo: "2026-12-31"
`webhook_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0May 11, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose that this is a read operation, nor any side effects, authorization needs, or return format. Only the basic listing function is mentioned.

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 clear sentence that front-loads the core purpose. No wasted words.

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

Completeness3/5

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

Given no output schema and moderate complexity (5 parameters, no required fields), the description adequately covers the input purpose but lacks information about return values or pagination. Schema fills many gaps.

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?

Schema description coverage is 80% (4 of 5 parameters have descriptions). The overall description adds minimal extra meaning: it frames the operation as a list with date filtering, which is already implied by the parameter names and 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 tool lists calendar events with date filters and specifies the calendar types (personal, group, company). It distinguishes from sibling tools like b24_calendar_create.

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

Usage Guidelines3/5

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

The description implies usage for listing events with date filters but does not provide explicit guidance on when to use versus alternatives or any exclusions. Sibling tools exist but are not referenced.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.