Skip to main content
Glama
Upload-Post

Upload-Post

Official

Manage the Telegram chat

manage_telegram_chat
Destructive

Read and administer the Telegram channel or group published by a profile via its bot, covering member moderation, invite links, topics, and chat settings.

Instructions

Read and administer the Telegram channel or group the profile publishes to, through the profile's own bot (it needs the matching admin rights). Fields go in params, with the API's names: get_info (include_administrators, return_bots: title, members count, admins); get_boosts (user_id); get_member (user_id; without it, the administrators); update_info (title, description, clear_description, photo_url, delete_photo, permissions, sticker_set_name; deleting the photo or changing permissions needs confirm); moderate_member (action: ban, unban, restrict, promote, demote, set_title, ban_sender_chat, unban_sender_chat, delete_all_reactions; user_id or sender_chat_id, until_date, revoke_messages, permissions, rights, custom_title; ban, restrict, promote, demote and delete_all_reactions need confirm); create_invite_link / edit_invite_link (invite_link, name, expire_date as Unix time, member_limit, creates_join_request); revoke_invite_link (invite_link) and new_primary_invite_link (the old primary link stops working) need confirm; answer_join_request (user_id, action approve or decline); forum topics: list_topic_icons, create_topic (name, icon_color, icon_custom_emoji_id), edit_topic (message_thread_id or general: true, action edit, close, reopen, hide, unhide, unpin_all), delete_topic (message_thread_id, needs confirm); unpin_all (every pinned message, needs confirm); leave_chat (the bot leaves: publishing there stops working, needs confirm).

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": {
      "action": "<action>",
      "user": "<user>"
    },
    "name": "manage_telegram_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesUpload-Post profile name with Telegram connected.
actionYes
paramsNoOther API fields for this action, with the REST API's own names (snake_case) and shapes. See the description for each action's fields. Leave out what you do not want to change.
confirmNoThe API's own confirmation for deletions and other changes that cannot be undone. Set it to true only after the user has approved that exact change; without it those actions are refused and nothing changes.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.25.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and openWorldHint=true; the description goes well beyond them by disclosing per-action consequences — the old primary invite link stops working, leaving the chat stops publishing, bans/deletions are irreversible and gated on `confirm`. That is exactly the behavioral context an agent needs before mutating a chat.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is front-loaded and every clause carries information, but it is delivered as one semicolon-chained wall of text across sixteen actions, which makes lookup onerous. A structured per-action breakdown would convey the same facts with far less parsing cost.

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?

An output schema exists, so return values need not be explained, and the description covers auth prerequisites, confirm gating, and every action's parameters. What's missing is edge-case behavior such as what happens when the bot lacks rights or when a member_limit/expire_date is invalid.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Because `params` is a free-form object, the schema itself cannot carry field semantics, so the description does the heavy lifting by spelling out the API field names and shapes per action (user_id/sender_chat_id, until_date, expire_date as Unix time, permissions vs rights, message_thread_id or general:true). Minor gap: it doesn't state which fields are required vs optional within each action beyond a few parentheticals.

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?

The description opens with a specific verb pair and resource: 'Read and administer the Telegram channel or group the profile publishes to, through the profile's own bot.' It then enumerates every action available (get_info, moderate_member, create_invite_link, forum topics, leave_chat), so an agent can distinguish this from manage_telegram_bot without opening the schema.

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?

It gives clear operating context: the bot needs matching admin rights, and destructive actions (ban, revoke_invite_link, delete_topic, leave_chat, new_primary_invite_link, unpin_all) require `confirm`. It does not name a sibling alternative or state when-not-to-use, but the per-action scope makes selection unambiguous.

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

Deploy Server

Other Tools