Skip to main content
Glama

b24_lists_element_list

Read-onlyIdempotent

Retrieve list elements (records) from a Bitrix24 information block with pagination, filtering, sorting, and field selection. Supports auto-pagination to fetch all matching records.

Instructions

List elements (records) of a list (lists.element.get) with pagination.

Field codes are usually PROPERTY_ for custom properties plus NAME, ID, CREATED_BY, etc. Use b24_call('lists.field.get', ...) to inspect field codes.

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.
iblock_idYesInformation-block id of the list (numeric IBLOCK_ID).
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.
iblock_type_idYesInformation-block type, e.g. 'lists' (portal lists), 'bitrix_processes' (workflows), 'lists_socnet' (group lists).
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
Behavior5/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds significant behavioral context: pagination offset/page size, auto-pagination with cap, filter operators, webhook precedence, and field code patterns. No contradictions with annotations.

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 with two sentences in the first paragraph and a second paragraph providing a helpful hint. It is front-loaded with purpose. No wasted sentences.

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?

Given the complexity (9 parameters, pagination, auto-fetch, webhook setup, field codes), the description covers all major aspects: purpose, pagination behavior, filter operators, fetch_all limits, webhook precedence, and references to related tools for field inspection. Output schema exists, so return values are not needed.

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 coverage is 100% with parameter descriptions. The description adds value by explaining field code patterns (PROPERTY_<n>), suggesting 'b24_call' to inspect fields, and clarifying that 'select' can include '*' or 'UF_*'. This enriches understanding beyond the 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 elements/records of a list with pagination, using the underlying API method 'lists.element.get'. It specifies the resource and verb, and hints at field codes, distinguishing it from sibling tools like b24_lists_element_add.

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 does not explicitly contrast with alternatives or state when not to use this tool. Usage is implied from the purpose, but no explicit when/when-not guidance is provided.

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