Skip to main content
Glama
Hermoso

Hermoso

Official

Post to Telegram

post_to_telegram
Destructive

Publish text, images, videos, albums, buttons, or files directly to a Telegram channel, group, or chat as the brand's own bot.

Instructions

Use this when the user wants to post to a Telegram channel or group. Publishing costs no credits. 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. @yourchannel) or its numeric id (a group is negative; a supergroup or channel starts with -100). 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. 0 credits. Connect at Connectors > Telegram. Full rules: get_instructions({topic:'post_to_telegram'}).

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": {
      "chatId": "<chatId>"
    },
    "name": "post_to_telegram"
  }
}

Input Schema

NameRequiredDescriptionDefault
hookNothe post's angle — a list_hooks id or your own wording, reused exactly
textNothe message. ≤4096 characters on its own; ≤1024 once any image or video is attached.
brandNoWHICH PROFILE this post belongs to — id or exact name from list_brands (a shared workspace: its profile id). Beats the connection's pin for THIS CALL ONLY; a name that matches no profile, or two, is REFUSED and nothing is posted.
chatIdYesREQUIRED — the destination: a public channel's @username, or the numeric chat id. Never guessed; ask the user, or use list_telegram_chats.
ideaIdNoshort id of the content-plan idea this post came from
recipeNothe post's FORMAT id, e.g. "slideshow" or "imessage_chat" — post_performance groups by it, so reuse one id per format
silentNodeliver without a notification sound (Telegram’s silent-delivery setting). 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 profile has more than one telegram account connected (several and none named is refused by name, never guessed); omit when there is one.
buttonsNoURL BUTTONS under the post, Telegram's call to action: [{text:'Shop now', url:'https://…'}] one per row, or rows [[a,b],[c]]. URL buttons only (https://, http:// or tg://), optional style danger|success|primary. A single photo, a video or a text post can carry them; an ALBUM cannot (Telegram's sendMediaGroup takes no buttons), so that combination is refused.
subjectNowhat the post is about
imageUrlNoone image (≤10MB after upload); a URL, not a local file path; use upload_file for local files
videoUrlNoone video (≤50MB). Passed alongside imageUrls it joins the album as one more item; a URL, not a local file path; use upload_file for local files
coverAtMsNoTHE VIDEO COVER in the chat, as ONE frame: milliseconds from the start (7000 = the frame at 7s). Sent as Telegram’s cover image; beats platformCover.
imageUrlsNoan ALBUM of 2–10 media, in order. Photos and videos may be mixed — Telegram allows it.
parseModeNo'HTML' to format the text with Telegram's HTML: <b>, <i>, <u>, <s>, <a href="…">, <code>, <pre>, <blockquote>, <tg-spoiler>. Omit for plain text (the default). In HTML mode a literal <, > or & in the copy must be written &lt; &gt; &amp;, which is why it is never turned on by itself. Markdown (**bold**) is NOT parsed; convert it to HTML tags.
documentUrlNosend a FILE (≤50 MB) as the post, text as caption; not with image/video
platformCoverNoVIDEO COVER. Omit it (the default) and Hermoso sets the video’s best frame — the same frame as its Library thumbnail — as the cover (Telegram’s in-chat video cover). true = send no cover and let the platform pick (usually the first frame). A cover you pass yourself always wins.
allowDuplicateNopost it even though an identical post was just made
disablePreviewNosuppress the link-preview card on a text-only post. Default is Telegram’s own behaviour (previews on).
idempotencyKeyNoany stable string: a repeat within 24h returns the original post instead of posting again
protectContentNono forwarding or saving

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.571
    • addedInput schema / properties / documentUrl
      Added value: +{
      +  "description": "send a FILE (≤50 MB) as the post, text as caption; not with image/video",
      +  "type": "string"
      +}
    • addedInput schema / properties / protectContent
      Added value: +{
      +  "description": "no forwarding or saving",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / silent / description
      Previous value: -"deliver without a notification sound (Telegram’s disable_notification). This is NOT a visibility setting — the message is just as visible."New value: +"deliver without a notification sound (Telegram’s silent-delivery setting). This is NOT a visibility setting — the message is just as visible."
  2. Changed2 schema fields changedv0.1.525
    • changedInput schema / properties / imageUrl / description
      Previous value: -"one image (≤10MB after upload)"New value: +"one image (≤10MB after upload); a URL, not a local file path; use upload_file for local files"
    • changedInput schema / properties / videoUrl / description
      Previous value: -"one video (≤50MB). Passed alongside imageUrls it joins the album as one more item."New value: +"one video (≤50MB). Passed alongside imageUrls it joins the album as one more item; a URL, not a local file path; use upload_file for local files"
  3. Changed2 schema fields changedv0.1.465
    • addedInput schema / properties / buttons
      Added value: +{
      +  "description": "URL BUTTONS under the post, Telegram's call to action: [{text:'Shop now', url:'https://…'}] one per row, or rows [[a,b],[c]]. URL buttons only (https://, http:// or tg://), optional style danger|success|primary. A single photo, a video or a text post can carry them; an ALBUM cannot (Telegram's sendMediaGroup takes no buttons), so that combination is refused.",
      +  "items": {
      +    "anyOf": [
      +      {
      +        "properties": {
      +          "style": {
      +            "enum": [
      +              "danger",
      +              "success",
      +              "primary"
      +            ],
      +            "type": "string"
      +          },
      +          "text": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "text",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      {
      +        "items": {
      +          "properties": {
      +            "style": {
      +              "enum": [
      +                "danger",
      +                "success",
      +                "primary"
      +              ],
      +              "type": "string"
      +            },
      +            "text": {
      +              "type": "string"
      +            },
      +            "url": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "text",
      +            "url"
      +          ],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      }
      +    ]
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / parseMode
      Added value: +{
      +  "description": "'HTML' to format the text with Telegram's HTML: <b>, <i>, <u>, <s>, <a href=\"…\">, <code>, <pre>, <blockquote>, <tg-spoiler>. Omit for plain text (the default). In HTML mode a literal <, > or & in the copy must be written &lt; &gt; &amp;, which is why it is never turned on by itself. Markdown (**bold**) is NOT parsed; convert it to HTML tags.",
      +  "enum": [
      +    "HTML"
      +  ],
      +  "type": "string"
      +}
  4. Changed2 schema fields changedv0.1.374
    • changedInput schema / properties / account / description
      Previous value: -"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."New value: +"WHICH connected account of this channel to post as — its @handle or id from list_connector_accounts. Needed only when the profile has more than one telegram account connected (several and none named is refused by name, never guessed); omit when there is one."
    • changedInput schema / properties / brand / description
      Previous value: -"WHICH BRAND this post belongs to — id or exact name from list_brands (a shared workspace: its profile id). Beats the connection's pin for THIS CALL ONLY; a name that matches no brand, or two, is REFUSED and nothing is posted."New value: +"WHICH PROFILE this post belongs to — id or exact name from list_brands (a shared workspace: its profile id). Beats the connection's pin for THIS CALL ONLY; a name that matches no profile, or two, is REFUSED and nothing is posted."
  5. Changed2 schema fields changedv0.1.320
    • changedInput schema / properties / brand / description
      Previous value: -"WHICH BRAND this post belongs to — the id or exact name from list_brands (a workspace shared with you: its profile id). Use it whenever the account has more than one brand and you are not certain which one this connection is pinned to: it beats the pin for THIS CALL ONLY and changes nothing about the connection. A name that matches no brand, or two brands, is REFUSED and nothing is posted — never resolved to the pin, which is the account you were guarding against."New value: +"WHICH BRAND this post belongs to — id or exact name from list_brands (a shared workspace: its profile id). Beats the connection's pin for THIS CALL ONLY; a name that matches no brand, or two, is REFUSED and nothing is posted."
    • addedInput schema / properties / coverAtMs
      Added value: +{
      +  "description": "THE VIDEO COVER in the chat, as ONE frame: milliseconds from the start (7000 = the frame at 7s). Sent as Telegram’s cover image; beats platformCover.",
      +  "type": "number"
      +}
  6. Changed6 schema fields changedv0.1.281
    • addedInput schema / properties / allowDuplicate
      Added value: +{
      +  "description": "post it even though an identical post was just made",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / hook
      Added value: +{
      +  "description": "the post's angle — a list_hooks id or your own wording, reused exactly",
      +  "type": "string"
      +}
    • addedInput schema / properties / ideaId
      Added value: +{
      +  "description": "short id of the content-plan idea this post came from",
      +  "type": "string"
      +}
    • addedInput schema / properties / idempotencyKey
      Added value: +{
      +  "description": "any stable string: a repeat within 24h returns the original post instead of posting again",
      +  "type": "string"
      +}
    • addedInput schema / properties / recipe
      Added value: +{
      +  "description": "the post's FORMAT id, e.g. \"slideshow\" or \"imessage_chat\" — post_performance groups by it, so reuse one id per format",
      +  "type": "string"
      +}
    • addedInput schema / properties / subject
      Added value: +{
      +  "description": "what the post is about",
      +  "type": "string"
      +}
  7. Changed1 schema field changedv0.1.272
    • addedInput schema / properties / brand
      Added value: +{
      +  "description": "WHICH BRAND this post belongs to — the id or exact name from list_brands (a workspace shared with you: its profile id). Use it whenever the account has more than one brand and you are not certain which one this connection is pinned to: it beats the pin for THIS CALL ONLY and changes nothing about the connection. A name that matches no brand, or two brands, is REFUSED and nothing is posted — never resolved to the pin, which is the account you were guarding against.",
      +  "type": "string"
      +}
  8. Changed1 schema field changedv0.1.256
    • addedInput schema / properties / platformCover
      Added value: +{
      +  "description": "VIDEO COVER. Omit it (the default) and Hermoso sets the video’s best frame — the same frame as its Library thumbnail — as the cover (Telegram’s in-chat video cover). true = send no cover and let the platform pick (usually the first frame). A cover you pass yourself always wins.",
      +  "type": "boolean"
      +}
  9. 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"
      +}
  10. Addedv0.1.161

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, openWorldHint=true) it discloses the permission requirement for the bot to be present in the chat and admin, the exact failure mode ('add it rather than reconnect'), credit cost, the album-vs-buttons restriction, and media size ceilings. These are operational facts an agent cannot derive from the annotations or schema.

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?

Usage context is front-loaded and the sentences are dense with actionable constraints, but 'Publishing costs no credits' is immediately repeated as '0 credits', and the all-caps emphasis adds noise without new information. Still compact for the complexity covered.

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 21-parameter mutation with no output schema it covers the decisive risks: destination resolution, bot permissions, refusal conditions, and where to find full rules. The one gap is that it never says what a successful publish returns (post id, link, status), which an agent may need for follow-up calls.

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 description coverage is 100%, so every one of the 21 parameters is already documented in the schema, including chatId format, HTML parseMode pitfalls and platformCover precedence. The description body mostly restates the chatId requirement rather than adding new meaning beyond the schema, so the baseline 3 applies.

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 names a specific verb and resource — publish a post to a Telegram channel, group or chat as the brand's own bot — and the leading 'Use this when the user wants to post to a Telegram channel or group' pins the triggering intent. Platform-specific nouns (@username channel ids, bot membership) make it unmistakable against siblings like post_to_slack or post_to_discord.

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?

It states the use case, names list_telegram_chats as the way to resolve the destination and get_instructions({topic:'post_to_telegram'}) for the full rule set, and gives the setup prerequisite (Connectors > Telegram). The 'chatId is never guessed, ask the user' rule is explicit behavioural routing rather than an inference.

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