Skip to main content
Glama
Sign In
Telegram MCP Server

Telegram MCP Server

by germankingerman-byte
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Pin Telegram Message

telegram_pin_chat_message
Idempotent

Pin a specific message to the top of a Telegram chat. Requires the bot to have the 'can_pin_messages' admin permission in groups or channels.

Instructions

Pin a message at the top of a chat. Requires the bot to have pin permissions in groups/channels (not required for private chats with the bot).

Args:

  • chat_id (string | number): Target chat

  • message_id (number): ID of the message to pin

  • disable_notification (boolean): Pin silently (default: false)

Returns: Confirmation of pinning.

Error Handling:

  • "not enough rights" -> the bot needs the 'can_pin_messages' admin permission in this chat.

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": {
      "chat_id": "<chat_id>",
      "message_id": "<message_id>"
    },
    "name": "telegram_pin_chat_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idYesTarget chat. Use a numeric chat ID (e.g. 123456789 for a user, -1001234567890 for a supergroup/channel) or a public channel username with a leading '@' (e.g. '@my_channel'). If unknown, call telegram_get_updates after the user messages the bot to discover it.
message_idYesID of the message to pin
disable_notificationNoIf true, pins silently without notifying chat members

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=false, destructiveHint=false, idempotentHint=true. The description adds context by confirming that pinning is a mutation that returns a confirmation, and includes error handling for permission issues. It does not contradict annotations.

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 extremely concise with no wasted words. It is front-loaded with the purpose, followed by a structured Args section and error handling. Every sentence adds value.

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 that the tool has 3 parameters, no output schema, and comprehensive annotations, the description covers the essential behavioral aspects: permission preconditions, parameter defaults, and known error cases. It could mention return structure (e.g., 'returns a message object'), but the current level is sufficient for an agent to use the tool correctly.

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 description coverage is 100%, so baseline is 3. The description adds value by including error handling context ('can_pin_messages' permission) and specifying the default for disable_notification. This goes beyond the schema's parameter 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 'Pin a message at the top of a chat.' It uses a specific verb ('Pin') and resource ('message at the top of a chat'), and distinguishes from sibling tools like telegram_unpin_chat_message.

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 provides guidance on when the tool can be used by specifying permission requirements: 'Requires the bot to have pin permissions in groups/channels (not required for private chats with the bot).' It also gives an error handling example that helps agents diagnose issues. However, it does not explicitly compare usage against alternatives.

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

Deploy Server

Other Tools