Skip to main content
Glama
overpod

MCP Telegram

telegram-set-business-intro

Set or clear your Telegram Business intro card with a title, description, and optional sticker to welcome new users in private chats.

Instructions

Set Telegram Business intro card — title and description shown to new users opening your chat, with an optional sticker. Requires Telegram Business subscription. Pass clear=true to remove.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clearNoPass true to remove the intro card
titleNoIntro title (max 32 chars)
stickerIdNoSticker document ID (stringified long) — optional illustrative sticker. Requires stickerAccessHash and stickerFileReference.
descriptionNoIntro description (max 70 chars)
stickerAccessHashNoAccess hash of the sticker document (required with stickerId)
stickerFileReferenceNoHex-encoded file_reference bytes (required with stickerId)
Behavior3/5

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

The description adds context like subscription requirement and removal option beyond annotations. However, it does not disclose side effects such as overwriting existing settings or idempotency, and does not clarify that both title and description may be needed together.

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?

Two sentences: first on main action, second on removal. No redundant words. Efficient and direct.

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?

Covers main use case and removal. Omits edge cases like calling with no parameters or conflicting clear with other params. Schema details fill some gaps, but description could include more behavioral completeness.

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%. The description adds meaning by explaining the role of title and description in the intro card and the removal behavior. It could be more explicit about the sticker parameter group requirement, but that is covered in the schema.

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 clearly states the tool sets the Telegram Business intro card, specifying title, description, and optional sticker. It distinguishes from sibling tools like set-business-away or set-business-greeting by focusing on the intro card.

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 mentions prerequisite of Telegram Business subscription and the removal option via clear=true. However, it does not explicitly exclude when to use alternatives or mention when not to use this tool.

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/overpod/mcp-telegram'

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