Check a Telegram group upgrade
telegram_get_group_upgrade_statusCheck 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
| Name | Required | Description | Default |
|---|---|---|---|
| operation_id | Yes | One 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
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| notice | No | Upgrading 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. | |
| status | Yes | ||
| chat_id | Yes | ||
| user_id | Yes | ||
| chat_title | Yes | ||
| created_at | Yes | ||
| dispatched | Yes | ||
| expires_at | Yes | ||
| new_chat_id | Yes | ||
| observed_at | Yes | ||
| operation_id | Yes | ||
| basic_group_id | Yes | ||
| trust_boundary | No | ||
| new_supergroup_id | Yes |