Bitrix24 MCP server

b24_products_list

Retrieve products from the catalog filtered by section, price range, active status, and other criteria. Specify fields to return for targeted results.

Instructions

Lista productos del catálogo con filtros por sección, precio, estado activo, etc.

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

Input Schema

Name	Required	Description
`filter`	No	Filtros. Ejemplo: { "SECTION_ID": 5, "ACTIVE": "Y" } o { ">=PRICE": 100, "<=PRICE": 500 } para rango de precios
`select`	No	Campos a retornar. Default: ID, NAME, ACTIVE, PRICE, CURRENCY_ID, SECTION_ID
`all_pages`	No
`webhook_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0May 11, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description fails to disclose behavioral traits such as read-only nature, pagination behavior, or data volume limits. The all_pages parameter hints at pagination but is not explained. The agent lacks understanding of side effects or constraints.

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 concise at one sentence, front-loading the purpose. However, it is minimal and does not include structured details like pagination or async callback (webhook). It earns its place but could be more informative.

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 description lacks completeness for a tool with 4 parameters and no output schema. It does not explain pagination (all_pages), async callback (webhook_url), or return format. For a list tool, the agent needs to know how to iterate pages and what data is returned. The description is insufficient.

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?

The description provides general context that the tool filters by section, price, active status, which aligns with the filter parameter. However, it does not explain the all_pages and webhook_url parameters, leaving gaps. Schema coverage is 50%, and the description partially compensates for the filter parameter but not for the other two.

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 it lists products from the catalog with filters by section, price, active status, etc. This distinguishes it from sibling tools like b24_products_get (single product retrieval) and b24_products_create (creation).

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 products with filters, but does not explicitly state when to use this tool versus alternatives like b24_products_get for single product retrieval. No when-not or alternative guidance is provided.

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