telegram-mcp

Overview Schema Source Related Servers Discussions Admin

get_participants

Retrieve the list of participants from any Telegram group or channel by providing its chat ID. Use an optional limit to control the number of members returned.

Instructions

List members of a group or channel

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chat_id": "<chat_id>"
    },
    "name": "get_participants"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`chat_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Aug 30, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'List members,' which implies a read operation, but it does not mention pagination/limit behavior, required permissions, what member data is returned, or whether results are complete for large groups or channels.

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 a single short sentence with a front-loaded verb-resource-object structure. Every word earns its place and there is no filler or redundancy.

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?

For a tool with no annotations and no output schema, this description is too thin to fully support correct invocation. It makes the overall purpose clear, but omits behavioral details like pagination, return shape, and how limit interacts with fetching all participants, which an agent would likely need.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for both parameters. 'Group or channel' clarifies that chat_id refers to a chat identifier for groups/channels, but the limit parameter is not explained, and no additional meaning or formatting guidance is provided beyond the schema's type and default.

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?

States a clear verb and resource: 'List members of a group or channel.' It identifies the target as a group or channel, helping distinguish from user/contact tools. It does not explicitly differentiate from sibling list/info tools like get_chat_info or list_chats, so it stops short of a 5.

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 phrase 'of a group or channel' gives useful context and implies this is the tool to call when member lists are needed. However, it does not explicitly say when not to use it or compare it with alternatives such as get_chat_info, list_chats, add_participant, or remove_participant.

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