Skip to main content
Glama
telegram-channels-mcp

telegram-channels-mcp

publish_post

Destructive

Publish a text or image post to your own Telegram channel, sending only after a preview and explicit confirmation token approval.

Instructions

Publish a post to the user's own channel, optionally with one image. DANGEROUS: the post becomes visible to all subscribers. Without confirm_token nothing is sent: you get a preview and a confirm_token. Show the preview to the user and repeat the call with the same arguments and confirm_token ONLY after the user explicitly approves this exact text and channel. image: local .jpg/.jpeg/.png/.webp/.gif file or https URL. With an image the caption limit is 1024 characters. markdown: bold, italic, code, text

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": {
      "channel": "<channel>",
      "text": "<text>"
    },
    "name": "publish_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
imageNo
silentNo
channelYes
parse_modeNomarkdown
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructive and open-world behavior, but the description adds the consequences and mechanism: the post becomes visible to all subscribers, and a preview/confirm_token gate prevents accidental sends. It further discloses a behavioral constraint (1024-character caption limit when an image is attached) that is not derivable from 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.

Conciseness5/5

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

The DANGEROUS warning and the preview-gating rule are front-loaded, and every remaining line is operational (formats, caption limit, markdown syntax). No filler or restatement of the tool name.

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?

Given a destructive, open-world publish operation, the description covers safety, the confirm flow, and most parameter behaviors, and an output schema exists so return values need no explanation. Only the undocumented 'silent' flag and 'channel' expectations keep it from being complete.

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 0% across 6 params, so the description must compensate, and it does for most: accepted image formats and URL support, markdown syntax for parse_mode, caption limit for text, and the semantics of confirm_token. The 'silent' parameter and the exact expectations for 'channel' are never mentioned, leaving a real gap.

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 and resource ('Publish a post') plus the scope constraint ('to the user's own channel'), which is exactly what separates it from a comment-reply or message tool. An agent can identify the action and target 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 an explicit two-phase protocol: call without confirm_token to get a preview, show it to the user, and repeat with the same arguments plus token ONLY after explicit approval of that exact text and channel. It also states the negative case ('nothing is sent'), leaving no ambiguity about when the side effect occurs.

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