Bitrix24 MCP server

b24_read_automations

Reads automation rules by stage, listing robots and triggers with their conditions and actions.

Instructions

Lee reglas de automatización (robots y triggers) por etapa con condiciones y acciones.

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_read_automations"
  }
}

Input Schema

Name	Required	Description	Default
`webhook_url`	No	URL del webhook (opcional si está configurado por defecto)
`entity_type_id`	No	ID del tipo de entidad (opcional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0May 11, 2026

TDQS

C2.9/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 the full burden of behavioral disclosure. It states that the operation is a read and that results include conditions and actions, but it does not explain how 'por etapa' maps to the schema, whether results are paginated, or what permissions are needed.

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 sentence with no filler and the verb is front-loaded. However, 'por etapa con condiciones y acciones' is slightly compressed and could mislead an agent into expecting a stage parameter that the schema does not define.

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?

For a simple read tool with zero required parameters and no output schema, the description conveys the core resource and content. However, it does not describe the return structure or clarify how entity_type_id relates to stages, leaving minor but relevant 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?

Both parameters are fully documented in the schema (webhook_url and entity_type_id), so the baseline is 3. The description adds no parameter-level meaning and even introduces the term 'etapa', which does not correspond to any schema property.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Lee' (reads), names the resource 'reglas de automatización (robots y triggers)', and adds scope with 'por etapa con condiciones y acciones'. This clearly communicates the tool's function, though it does not explicitly differentiate it from similar siblings like b24_bizproc_list.

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?

There is no guidance on when to use this tool versus alternatives such as b24_bizproc_list or b24_read_entity_types. The verb 'Lee' implies a read operation, but no prerequisites, exclusions, or selection context are provided.

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