Skip to main content
Glama

channels_connect_telegram_bot

🤖 Connect a Telegram Bot (Bot API) channel from its bot token.

When to use:

  • After a bot was created via @BotFather and you have its token.

  • The token alone is sufficient — no Telegram user account is needed.

Validates the token, creates the channel account, and registers the webhook so the bot starts receiving messages immediately.

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": {
      "bot_token": "<bot_token>"
    },
    "name": "channels_connect_telegram_bot"
  }
}

Input Schema

NameRequiredDescriptionDefault
bot_tokenYesTelegram bot token from @BotFather (e.g. '123456789:ABCdef...'), or a `clip:` handle from clipboard.copy (the token from the BotFather message, or from a bot connected in another workspace) so the token is never seen.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / bot_token / description
      Previous value: -"Telegram bot token from @BotFather (e.g. '123456789:ABCdef...')."New value: +"Telegram bot token from @BotFather (e.g. '123456789:ABCdef...'), or a `clip:` handle from clipboard.copy (the token from the BotFather message, or from a bot connected in another workspace) so the token is never seen."
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added
  4. Removed
  5. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations declare non-read-only, open-world, non-idempotent but non-destructive, and the description meaningfully adds side-effect detail beyond them: the token is validated, a channel account is created, and a webhook is registered so messages flow immediately. It does not cover failure behavior when the token is invalid, which is the main remaining gap.

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?

Front-loaded one-line purpose followed by a short bulleted usage block, then a single sentence of behavior. No redundant restatement of the schema or annotations.

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 two-parameter creation tool with annotations present and no output schema, the description covers prerequisites, validation, account creation, and webhook registration — enough to call it correctly. Only the response shape and invalid-token handling are left unstated, which is minor.

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%, with both bot_token (including the clip: handle form) and in_workspace fully documented in the schema. The description confirms the token is the only required input but adds no new semantics about in_workspace or the clip: indirection, so baseline 3 applies.

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 description opens with a specific verb and resource: 'Connect a Telegram Bot (Bot API) channel from its bot token,' and states that the token alone is the input. It is clearly scoped to Telegram Bot API and distinguishable from generic channel tools, though it never names a sibling such as channels_connect to contrast with.

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

Usage Guidelines4/5

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

An explicit 'When to use' block gives the prerequisite (a bot created via @BotFather with its token) and a clarifying non-requirement ('no Telegram user account is needed'). It stops short of stating when to prefer a different connector tool instead, so it is strong context without exclusions.

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.