Skip to main content
Glama
Telegram MCP

Telegram MCP

Check a Telegram group upgrade

telegram_get_group_upgrade_status
Read-onlyIdempotent

Check the status of a Telegram group upgrade using the same operation_id to recover the original and new chat IDs after a timeout or lost connection, without starting a new migration.

Instructions

Read an existing upgrade and reconcile its exact original group without retrying.

Available even when group upgrades are disabled. Reuse the SAME operation_id after a timeout, lost connection or restart. Never prepare a replacement ID or call a new migration to resolve an unknown result. Returns both the old and new chat IDs when Telegram confirms the migration relationship.

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": {
      "operation_id": "<operation_id>"
    },
    "name": "telegram_get_group_upgrade_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
operation_idYesOne UUID as 32 lowercase hexadecimal characters for this exact account-bound group upgrade. Use the SAME ID for prepare, apply and status, including after timeout; never create a replacement retry ID.

Output Schema

NameRequiredDescriptionDefault
errorNo
noticeNoUpgrading deactivates the original basic group and creates a supergroup with a new chat ID. Retain both chat IDs for historical messages and searches. There is no automatic rollback.
statusYes
chat_idYes
user_idYes
chat_titleYes
created_atYes
dispatchedYes
expires_atYes
new_chat_idYes
observed_atYes
operation_idYes
basic_group_idYes
trust_boundaryNo
new_supergroup_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.14.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is known; the description adds non-obvious behavior on top: availability under disabled upgrades, idempotent-safe reuse of the same ID across restarts, and that the response carries both old and new chat IDs once Telegram confirms the relationship. It does not describe what is returned when the migration is not yet confirmed, leaving one behavioral corner uncovered.

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?

Content is front-loaded with the purpose, then the availability caveat, then the retry rule, then the return shape. It is efficient, though the retry instruction appears twice in slightly different wording ('without retrying' / 'Reuse the SAME operation_id' / 'Never prepare a replacement ID'), which is mild redundancy rather than waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with an output schema, this covers what an agent needs: prerequisites (single account-bound upgrade), the retry protocol, and a pointer to the return values. The only gap is the non-terminal case, i.e. what a caller should do if status reports the migration is not yet confirmed, which is not addressed.

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 already states the 32-lowercase-hex pattern and the 'use the SAME ID for prepare, apply and status' rule, so the description's operation_id guidance largely restates structured data. The baseline 3 applies; no new format, derivation or scoping detail is added beyond the schema.

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 first sentence states a specific verb and resource: 'Read an existing upgrade and reconcile its exact original group without retrying.' It is clearly distinct from the sibling status/get tools (pins, drafts, history), which deal with unrelated chat resources. Slightly held back from 5 because 'reconcile' is jargon that only becomes clear after reading the retry discussion.

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

Usage Guidelines5/5

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

It gives explicit conditions for use (after a timeout, lost connection or restart, or when the result is unknown) and explicit exclusions ('Never prepare a replacement ID or call a new migration'). It also removes a common blocker by stating the tool is 'Available even when group upgrades are disabled,' so the agent knows not to bail out early.

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