Skip to main content
Glama
overpod

MCP Telegram

telegram-toggle-story-pinned

Pin or unpin stories in your Telegram profile highlights to manage which stories are featured (up to 3).

Instructions

Pin or unpin stories in your profile highlights (Telegram allows up to 3 pinned stories).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesStory IDs to pin or unpin
chatIdNoPeer owning the storiesme
pinnedYestrue to pin, false to unpin
Behavior4/5

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

The description adds useful behavioral context beyond annotations: it specifies that the action affects profile highlights and reveals the Telegram limit of 3 pinned stories. Annotations indicate readOnlyHint=false (mutation) and openWorldHint=true, which are consistent. No contradictions.

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 description is a single sentence that conveys the essential purpose and a key constraint. It is front-loaded with the action and resource, and every word adds value. No unnecessary information.

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 the tool's simplicity (3 parameters, no output schema), the description is largely complete. It explains what the tool does and a critical constraint. Minor gap: could mention that max 3 applies to total pinned, but not critical for basic usage.

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?

Input schema has 100% coverage with descriptions for all parameters (ids, chatId, pinned). The description does not add additional meaning to the parameters beyond what the schema provides. Baseline score of 3 is appropriate.

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 action (pin or unpin), the resource (stories), the context (profile highlights), and includes a specific constraint (Telegram allows up to 3 pinned stories). It clearly distinguishes from sibling tools like pin-message and pin-chat.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool vs alternatives. It mentions a constraint (up to 3 pinned stories) which implies a usage condition, but lacks explicit guidance on when not to use or comparisons with similar tools.

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