Skip to main content
Glama

b24_tasks_list

Read-onlyIdempotent

List Bitrix24 tasks using customizable filters, sorting, and pagination. Supports auto-pagination to retrieve all matching records.

Instructions

List tasks with filtering, sorting, and pagination (tasks.task.list).

Common filter keys: RESPONSIBLE_ID, CREATED_BY, GROUP_ID (project/group), STATUS (1 new,2 pending,3 in progress,4 supposedly done,5 completed,6 deferred), STAGE_ID (kanban column), >=CREATED_DATE, etc. Common select: ['ID','TITLE','STATUS','RESPONSIBLE_ID','GROUP_ID','CREATED_BY', 'DEADLINE','STAGE_ID','COMMENTS_COUNT','TAGS'].

Caveat for Scrum sprint boards (confirmed live, not just theoretical): STAGE_ID here is reliable for a regular group kanban, but for a task on an active sprint it goes stale the moment the card is moved the correct way (b24_scrum_task_move / a real drag on the board) — Bitrix tracks that move in a separate structure with no public method to read it back. Filtering by STAGE_ID on a sprint board is approximate at best.

Returns: JSON pagination envelope {items, count, total, next, has_more, truncated}.

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 (readOnlyHint, destructiveHint, idempotentHint) already provide safety profile. The description adds critical behavior: STAGE_ID unreliability on sprint boards, pagination behavior, auto-pagination with fetch_all, and return shape. No contradiction. Adds value beyond 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?

Description is well-structured: summary line, common filter/select details, caveat section, return format. It is informative but not overly verbose; the caveat is necessary and justified.

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?

For a complex list tool with 7 parameters and existing output schema, the description covers filtering, sorting, pagination, auto-pagination, webhook override, and a crucial behavioral caveat. No gaps identified.

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

Parameters5/5

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

Schema coverage is 100% (baseline 3). Description enriches parameters with common filter keys (RESPONSIBLE_ID, STATUS values, etc.), select fields, filter operator prefixes, fetch_all behavior and cap, and webhook fallback precedence. This significantly aids agent understanding.

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 clearly states 'List tasks with filtering, sorting, and pagination' and specifies the API method (tasks.task.list). It identifies the resource (tasks) and provides specific details, though it does not explicitly differentiate from sibling task-related list tools like b24_task_comments_list.

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?

No explicit guidance on when to use this tool versus alternatives. The description includes a caveat about STAGE_ID on sprint boards, which offers usage caution, but lacks direct comparisons or when-not-to-use advice.

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