Skip to main content
Glama
Upload-Post

Upload-Post

Official

Manage the Telegram bot

manage_telegram_bot
Destructive

Manage your profile's Telegram bot settings: retrieve or update the bot profile, and get, set, or delete bot commands via the Upload-Post API.

Instructions

Profile and commands of the profile's own Telegram bot. Fields go in params: get_profile (language_code); update_profile (name, description, short_description, language_code, photo_url or animation_url, remove_photo with confirm, menu_button, default_administrator_rights, for_channels; clear_name / clear_description / clear_short_description); get_commands and delete_commands (scope, language_code; delete needs confirm); set_commands (commands: [{command, description}], 1-100, plus scope and language_code).

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

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/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the description's job is narrower and it delivers: it identifies which specific actions are irreversible (delete_commands, and the clear_name / clear_description / clear_short_description flags) and states that they require `confirm`. It also notes the mutually exclusive photo_url vs animation_url choice and the 1-100 bound on commands. It does not discuss permissions or rate limits, but that is a modest gap against annotation coverage.

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?

The content is dense but waste-free — every clause maps to an action's accepted fields. The single run-on parenthetical is harder to scan than a per-action list, and the first clause is a sentence fragment, but the scope statement is still front-loaded ahead of the field details.

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?

With an output schema present, the description needn't explain return values, and it covers all five enum actions plus their field sets and constraints. An agent can select an action and populate `params` correctly. What remains unstated is any prerequisite (e.g. that Telegram must be connected to the profile) beyond the schema's brief parameter hint.

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

Parameters5/5

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

The `params` object is free-form, so all of its meaning must come from prose — and the description enumerates the accepted fields per action, groups the clear_* flags under update_profile, and specifies structural requirements for set_commands (array of {command, description}, count 1-100). This is genuinely irreducible value that the schema cannot supply.

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 names a specific resource — "the profile's own Telegram bot" — and enumerates the five operations (get_profile, update_profile, get_commands, set_commands, delete_commands). This differentiates it from the sibling manage_telegram_chat, which handles chats. The opening fragment is terse rather than a clean sentence, but the verb/resource/scope are unambiguous.

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

Usage Guidelines3/5

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

The phrase "the profile's own Telegram bot" implicitly scopes usage versus chat operations, and the field lists show which action to pick for a given intent. However, there is no explicit when-to-use/when-not statement and no named alternative, so the agent must infer routing from the action names alone.

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