Skip to main content
Glama
overpod

MCP Telegram

telegram-set-personal-channel

Set a channel as your personal Telegram profile display. Pass a channel ID or @username to feature it, or use clear=true to remove it.

Instructions

Set the channel displayed on your profile as 'Personal Channel'. Pass clear=true to remove. Pass channelId or @username of a channel you own or are subscribed to.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clearNoPass true to remove personal channel from profile
channelIdNoChannel ID or @username to feature on profile
Behavior3/5

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

Annotations indicate mutation (readOnlyHint=false) and openWorldHint=true. The description confirms mutation but does not elaborate on side effects or reversibility. It adds ownership requirement but no behavioral details beyond that.

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 concise sentences that front-load the main purpose and efficiently cover both parameters. No unnecessary words.

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 simple action with no output schema, the description covers the operation, parameters, and a prerequisite. Missing details about success confirmation or error cases, but adequate for the complexity.

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% with good descriptions. The tool description adds context about using channelId or @username and the condition of ownership/subscription, which goes beyond the schema descriptions.

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 personal channel on the user's profile, with specific verbs 'Set' and 'remove', and distinguishes from siblings by focusing on this specific profile feature.

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?

The description explains when to use (set or clear personal channel) and mentions prerequisites (own or subscribed channel). It lacks explicit exclusions or alternatives, but no sibling tool directly competes.

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