Skip to main content
Glama

b24_group_list

Read-onlyIdempotent

List and filter Bitrix24 workgroups/projects by name, owner, subject, or status. Supports pagination, field selection, and sorting.

Instructions

List workgroups/projects (sonet_group.get) with a working filter.

Filter keys include NAME, '%NAME' (substring), ACTIVE ('Y'/'N'), CLOSED, OWNER_ID, SUBJECT_ID. Returns a pagination envelope of group objects (ID, NAME, DESCRIPTION, SCRUM_MASTER_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 declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds value by stating it returns a pagination envelope of group objects with specific fields, plus mentions the working filter behavior.

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?

The description is two sentences with no wasted words: first sentence states purpose, second lists filter keys and return info. It is optimally concise and front-loaded.

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 tool with 7 optional parameters, pagination, filtering, and an output schema, the description covers all essentials: purpose, filter keys, pagination envelope, and underlying method. It is complete given the complexity and annotations.

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 100%, and the schema itself provides detailed parameter descriptions. The description lists filter keys but does not add significant new meaning beyond the schema, meeting the baseline.

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 workgroups/projects with a filter, specifying the underlying API method (sonet_group.get). It distinguishes from sibling tools like b24_group_create, b24_group_update, etc., which are for other operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly lists filter keys (NAME, ACTIVE, etc.) and mentions pagination, providing clear context for usage. It does not include explicit exclusions or when-not-to-use, but the purpose is well-defined.

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