Ban a user from a Telegram supergroup or channel permanently by providing chat and user identifiers. Restrict access immediately until an unban is issued.
Ban a user from a supergroup or channel (permanent until unbanned)
| Name | Required | Description | Default |
|---|---|---|---|
| chatId | Yes | Chat ID or username | |
| userId | Yes | User ID or username to ban |
Changes observed during successful MCP inspections.
v1.36.5v1.36.3v1.36.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark as write operation. Description adds permanence detail but omits required permissions, side effects (user removal from group), and whether it purges message history. openWorldHint true suggests unstated effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, 11 words, immediately conveys action and scope. No redundant or extraneous information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Simple tool with no output schema, but description could mention admin permissions requirement and that ban is only for supergroups/channels. Lacks mention of reversal (unban). Adequate but not thorough.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers both parameters with descriptions. Tool description does not add format details (e.g., username vs numeric ID), so no extra value beyond schema. Baseline 3 due to full schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states verb 'ban', resource 'user', and context 'supergroup or channel' with permanence. Effectively distinguishes from sibling tools like 'kick' and 'unban'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Indicates permament ban but does not explicitly guide when to use versus alternatives like 'telegram-kick-user' or 'telegram-block-user'. No prerequisites or exclusion criteria provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.