Bitrix24 MCP server

b24_disk_folder_list

Retrieve the contents of a folder in Bitrix24 Disk, supporting optional filters. If no folder ID is provided, lists the user's root storage.

Instructions

Lista el contenido de una carpeta en el Disk de Bitrix24.

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

Input Schema

Name	Required	Description
`folder_id`	No	ID de la carpeta. Si no se indica, lista el storage raíz del usuario
`filter`	No	Filtros opcionales. Ejemplo: { "NAME": "Contratos" }
`webhook_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0May 11, 2026

TDQS

B3.4/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. It does not disclose behaviors like handling missing folder_id (defaults to root as per schema), error cases, or output format. Minimal transparency.

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?

A single, clear sentence with no wasted words. It is appropriately sized and front-loaded.

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?

The tool has 3 parameters and no output schema. The description does not mention the return format (list of files/folders) or any pagination, which leaves the agent underinformed for a list operation.

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 67% (folder_id and filter have descriptions). The tool description adds no extra meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 'Lista' and resource 'contenido de una carpeta en el Disk de Bitrix24'. It distinguishes the tool from siblings like b24_disk_file_get and b24_disk_storages.

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 folder contents but provides no explicit guidance on when to use this tool versus alternatives or when not to use it.

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