Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Post to Telegram

post_to_telegram

Publish text, images, videos, or mixed albums to a Telegram channel, group, or chat as your own bot. Specify the chat ID or @username; uploads media directly and returns the message link.

Instructions

Publish to a Telegram channel, group or chat as the brand's own bot. WHICH CHAT IS ALWAYS REQUIRED AND IS NEVER GUESSED: pass chatId as the public channel's @username (e.g. @hermosoai) or its numeric id (a group is negative; a supergroup or channel starts with -100). There is no default and there cannot be one — the Telegram Bot API publishes no method that lists the chats a bot belongs to, so Hermoso genuinely cannot know them. list_telegram_chats reports the chats that have MESSAGED the bot in the last 24 hours, which is a shortcut for finding an id and is NOT a roster: a chat missing from it can still be posted to. TEXT: up to 4096 characters on a text-only message, but only 1024 the moment ANY photo or video is attached — a caption is not a message, and Hermoso refuses the over-long one before spending the round trip and says which budget applied. MEDIA: one image (imageUrl), one video (videoUrl), or an ALBUM of 2–10 (imageUrls, in order) in which photos and videos may be MIXED — pass a videoUrl alongside imageUrls and it joins the album as one more item. Hermoso uploads the bytes rather than handing Telegram a link, which is what buys the larger ceilings: 10MB per photo and 50MB per video, where a link would be 5MB and 20MB. THE BOT MUST BE IN THE CHAT — an administrator with Post Messages for a channel, an unrestricted member for a group; if it is not, Telegram refuses and the error says to add it rather than to reconnect. Returns the message id and, for a PUBLIC chat, its t.me link — a private group has no public web link, so url comes back null rather than as a link that would 404 for whoever you hand it to. 0 credits. Connect at Settings ▸ Connectors ▸ Telegram, or here with connect_connector, by pasting a bot token from @BotFather.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNothe message. ≤4096 characters on its own; ≤1024 once any image or video is attached.
chatIdYesREQUIRED — the destination: a public channel's @username, or the numeric chat id. Never guessed; ask the user, or use list_telegram_chats.
silentNodeliver without a notification sound (Telegram’s disable_notification). This is NOT a visibility setting — the message is just as visible.
accountNoWHICH connected account of this channel to post as — its @handle or id from list_connector_accounts. Needed only when the brand has more than one telegram account connected (several and none named is refused by name, never guessed); omit when there is one.
imageUrlNoone image (≤10MB after upload)
videoUrlNoone video (≤50MB). Passed alongside imageUrls it joins the album as one more item.
imageUrlsNoan ALBUM of 2–10 media, in order. Photos and videos may be mixed — Telegram allows it.
disablePreviewNosuppress the link-preview card on a text-only post. Default is Telegram’s own behaviour (previews on).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.189
    • addedInput schema / properties / account
      Added value: +{
+  "description": "WHICH connected account of this channel to post as — its @handle or id from list_connector_accounts. Needed only when the brand has more than one telegram account connected (several and none named is refused by name, never guessed); omit when there is one.",
+  "type": "string"
+}
  2. Addedv0.1.161

TDQS

A4.8/5.0
Behavior5/5

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

Far exceeds the annotations. Annotations cover safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true); the description adds character budgets (4096 vs 1024 with media), upload size ceilings (10MB/50MB vs 5MB/20MB for links), the bot-membership precondition and its error shape, the return value (message id plus t.me link, null for private chats), and cost (0 credits). This is unusually rich behavioral disclosure.

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?

Front-loads the single most important constraint (chatId always required, never guessed) before any detail, which is exactly right. It is dense with genuine information, though the rhetorical emphasis ('There is no default and there cannot be one', 'a caption is not a message') adds length that a tighter phrasing could trim.

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?

No output schema exists, yet the description explains the return value (message id and, for public chats, the t.me link, null for private). For an 8-parameter tool with non-trivial media and account-selection logic, the description covers destination, content limits, media rules, preconditions, and cost — nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: the numeric-id conventions (negative for groups, -100 for supergroups/channels) and the album-mixing rule (a videoUrl alongside imageUrls joins as one more item). Much of the remaining content mirrors the schema, so it earns an increment rather than full marks.

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?

States a specific verb+resource ('Publish to a Telegram channel, group or chat as the brand's own bot') and immediately differentiates itself from the many sibling publishing tools (post_to_x, post_to_bluesky, post_to_linkedin) by naming Telegram explicitly. An agent can identify this tool's function 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 Guidelines5/5

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

Gives explicit routing guidance: chatId is always required and never guessed, list_telegram_chats is named as a discovery shortcut while being carefully distinguished from a roster, and the connect_connector setup path is stated. It also names the precondition (bot must be in the chat with the right role) that selects success vs. failure.

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