Skip to main content
Glama

Telegram: Connect

telegram_connect
Destructive

Connect or reconnect the user's Telegram account directly in the conversation: returns a QR code image to scan from Telegram > Settings > Devices > Link Desktop Device, then poll account_connection_status until connected. Accounts protected by a Telegram cloud password (2FA) must use the browser link returned by account_connect instead. Use account_id to re-authenticate an existing disconnected Telegram account.

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_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoNilyo connection ID (unipile_account_id from list_connected_accounts) of an EXISTING account to re-authenticate. Omit to connect a new account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the mutation-oriented annotations, the description discloses the QR-image result, required user interaction, asynchronous completion through status polling, and the 2FA limitation. It does not explain QR expiration, polling cadence, failure handling, or what destructive effects reconnection may have, so some operational behavior remains unspecified.

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 compact and front-loaded with the tool's purpose, then efficiently presents the output and workflow, the 2FA exception, and the reconnect parameter. Despite the detailed navigation path, every sentence contributes actionable information without filler.

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

Completeness5/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, fully documented parameter, this supplies enough context to select and invoke it correctly. Because there is no output schema, the explicit QR-code result is especially valuable, and the normal flow, completion check, exceptional 2FA route, and re-authentication case are all covered.

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 coverage is 100%, and the schema already identifies account_id as an existing account's Unipile connection ID, names list_connected_accounts as its source, and explains that omission connects a new account. The description usefully narrows the stated use case to an existing disconnected account but adds little parameter meaning beyond the schema.

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?

Clearly states the action and resource: connecting or reconnecting a Telegram account through an in-conversation QR-code flow. It also distinguishes this tool from account_connect, which supplies a browser link, and account_connection_status, which is used for subsequent polling.

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?

Provides explicit selection and workflow guidance: scan the QR code through the specified Telegram menu, poll account_connection_status, use account_connect for accounts with Telegram cloud-password 2FA, and supply account_id for re-authentication. These instructions cover the main alternative, prerequisite exception, and reconnect case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.