Telegram MCP Server

Overview Schema Source Related Servers Discussions Admin

telegram_get_chat_administrators

Retrieve the list of administrators for any Telegram chat, group, or channel. Use this to identify who has admin rights and manage permissions effectively.

Instructions

Get a list of administrators in a chat/group/channel.

:param chat_id: Target chat identifier. :return: JSON formatted list of ChatMember objects representing administrators.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "telegram_get_chat_administrators"
  }
}

Input Schema

Name	Required	Description	Default
`chat_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 26, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the return format (JSON list of ChatMember objects), but does not state whether the operation is read-only, what permissions are required, or how it behaves for invalid or null chat_id. This is a significant gap for an endpoint with no structured metadata.

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 extremely concise: two sentences plus a parameter doc line. It front-loads the purpose and includes no filler. Every line earns its place, making it easy for an agent to quickly parse.

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 one optional parameter and an output schema, the description leaves out critical context: whether chat_id can be omitted, required administrative permissions, and how the returned list is structured beyond 'JSON list'. This is insufficient for reliable agent invocation, especially without 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 0%, so the description must compensate. It provides a minimal semantic for chat_id ('Target chat identifier') which adds some meaning, but it does not explain the parameter's optionality (default null), accepted value formats, or what happens when omitted. It is adequate but far from comprehensive.

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 a specific verb and resource: 'Get a list of administrators in a chat/group/channel.' It distinguishes itself from siblings like get_chat and get_chat_member_count by targeting administrators specifically, covering multiple chat types.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., bot must be admin), no exclusions, and no naming of sibling tools that might be more appropriate in other contexts. The agent must infer usage from the name alone.

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

Deploy Server