Skip to main content
Glama

b24_crm_product_list

Read-onlyIdempotent

List CRM catalog products with filtering, sorting, and pagination. Supports auto-pagination to retrieve all matching records up to a limit.

Instructions

List classic CRM catalog products (crm.product.list) with pagination.

Common filter keys: NAME, SECTION_ID, ACTIVE ('Y'/'N'), CATALOG_ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderNoSort object, e.g. {'ID':'DESC'} or {'DATE_CREATE':'ASC'}.
startNoPagination offset (page size is 50). Use 'next' from a prior response.
filterNoBitrix filter object. Keys may carry operator prefixes: '>', '<', '>=', '<=', '!', '%' (substring), '=%', e.g. {">=DATE_CREATE": "2026-01-01", "%TITLE": "draft"}.
selectNoFields to return, e.g. ['ID','TITLE','*','UF_*']. Omit for defaults.
fetch_allNoAuto-paginate and return all matching records (capped by BITRIX_MAX_PAGES, default 40 pages = 2000 records). Use a filter to keep this bounded.
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
Behavior4/5

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

Annotations already mark as read-only and idempotent; description adds pagination behavior (offset, fetch_all, max pages) and filter operator syntax beyond what annotations provide.

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?

Two concise sentences, front-loaded with purpose and key details, no unnecessary text.

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

Completeness5/5

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

Covers all essential aspects: purpose, pagination, filter keys, and tool-specific parameters; output schema covers return values, making this description complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% parameter description coverage; description adds value by listing common filter keys (NAME, SECTION_ID, etc.) and explaining pagination (use 'next').

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?

Clearly states it lists classic CRM catalog products with pagination, distinguishing from sibling list tools by specifying 'classic CRM catalog'.

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 explicit guidance on when to use this tool over siblings like b24_catalog_product_list or b24_crm_list. Provides filter key suggestions but no usage context.

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