Skip to main content
Glama
Upload-Post

Upload-Post

Official

Manage the Telegram Business account

manage_telegram_business
Destructive

Manage a Telegram Business account: post, edit, delete and repost stories, update the profile, handle gifts, check stars balance and transfer stars, with a preview step before anything is sent.

Instructions

A Telegram Business account (the user's own Telegram account) connected to the profile's bot. Fields go in params with the API's names; business_connection_id picks the connection when the bot has several. connections (rights and whether each is enabled); get_profile; update_profile (first_name, last_name, username, bio, media_url for the photo with is_public, remove_photo, gift_settings); stories posted as the account: post_story (media_url: photo 1080x1920 up to 10 MB or video 720x1280 up to 30 MB and 60 s; active_period, caption, areas, post_to_chat_page, protect_content), edit_story (story_id and the fields), delete_story (story_id), repost_story (from_chat_id, from_story_id, active_period); gifts (the account's gifts), manage_gift (action convert|upgrade|transfer|delete, owned_gift_id, idempotency_key; irreversible, needs confirm); stars_balance, transfer_stars (star_count 1-10000 to the bot, idempotency_key; needs confirm). Needs the user's approval: call it first without confirmed to get a preview (nothing is sent), show the user exactly what will go out, and repeat the call with confirmed: true only after they approve.

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

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.
confirmedNoSet to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.26.5

TDQS

A4.7/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, and the description adds substantial behavior on top: manage_gift is called out as irreversible and needing `confirm`, transfer_stars has a 1-10000 star range and idempotency_key, post_story states exact media constraints (1080x1920 up to 10 MB, or 720x1280 up to 30 MB and 60 s), and the preview-first approval protocol is spelled out with the guarantee that the unconfirmed call sends nothing. This is the kind of detail that prevents accidental irreversible actions.

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?

Nothing is wasted - every clause carries an action, a field, or a constraint - and the account scoping plus the confirmation protocol bracket the action list sensibly. The downside is that the action catalogue is one long run-on paragraph with deeply nested parentheticals, so it is dense to parse; a bulleted action list would serve readability better at this length.

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?

An output schema exists, so return values need not be described, and the description covers the hard parts of an eleven-action multiplexer: field names per action, ambiguity resolution via business_connection_id, media limits, irreversibility, and the preview/approve protocol. The few actions given only a short gloss (gifts, stars_balance, connections) are self-descriptive and their payloads are covered by the output schema.

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?

With 80% schema coverage the schema baseline is already high, but the description goes well beyond it: it documents per-action fields for update_profile (including gift_settings, remove_photo, is_public), post_story (active_period, caption, areas, post_to_chat_page, protect_content), repost_story, manage_gift and transfer_stars, and it introduces business_connection_id, which is not a top-level schema property. It also tells the agent to use the REST API's own snake_case names inside `params` and to omit fields not being changed.

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 opening sentence defines the resource precisely ('A Telegram Business account (the user's own Telegram account) connected to the profile's bot'), which separates it from bot- and chat-oriented siblings. It then enumerates all eleven actions (connections, get_profile, update_profile, post_story, edit_story, delete_story, repost_story, gifts, manage_gift, stars_balance, transfer_stars) with a specific verb or resource for each, so an agent can pick the right action 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 operational guidance: business_connection_id selects the connection when the bot has several, and the closing passage prescribes the exact two-step flow (call without `confirmed` for a preview, show the user, then repeat with `confirmed: true`). What it lacks is routing guidance against alternatives - e.g. when to use this versus manage_telegram_bot, manage_telegram_chat, or manage_telegram_payments, which overlaps with stars_balance/transfer_stars.

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