Skip to main content
Glama
FantomaSkaRus1

telegram-bot-mcp

send_paid_media

Send media to a chat with a required payment in Telegram Stars. Define the price and media array, and optionally add a caption with formatting.

Instructions

Send paid media to a chat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mediaYesJSON array of InputPaidMedia objects
captionNoCaption for the media
chat_idNoChat ID. Optional — defaults to log group
parse_modeNoCaption formatting
star_countYesPrice in Telegram Stars
protect_contentNoProtect from forwarding
caption_entitiesNoJSON array of MessageEntity
reply_parametersNoJSON ReplyParameters object
message_thread_idNoTopic/thread ID
disable_notificationNoSend silently
show_caption_above_mediaNoShow caption above media
Behavior1/5

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

The description does not disclose key behavioral traits: that it deducts Telegram Stars, requires InputPaidMedia, or any side effects. No annotations are provided, so the description carries full burden but fails to inform about costs or media type constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is only one sentence, which is too brief given the tool's complexity (11 parameters, no annotations). It under-specifies the tool's purpose and behavior, sacrificing usefulness for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 11 parameters, no output schema, and zero annotations, the description is extremely incomplete. It fails to explain what paid media involves, when to use the tool, or how parameters interact. Crucial context is missing.

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 each parameter already has a description. The tool description adds no extra meaning beyond the schema, meeting the baseline of 3.

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 clearly states the action 'send' and the resource 'paid media' to a chat. It distinguishes from sibling tools like send_photo or send_video by specifying 'paid media', though it does not elaborate on what makes media 'paid'.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives such as send_photo or send_media_group. There is no mention of prerequisites like having sufficient Telegram Stars or that this tool is for monetized content.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FantomaSkaRus1/telegram-bot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server