Skip to main content
Glama
Sign In
Telegram MCP Server

Telegram MCP Server

by ivantelix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

telegram_pin_chat_message

Pin a message in a group, supergroup, or channel to keep it prominent. Specify message ID and optionally chat ID to pin silently without notifications.

Instructions

Pin a message in a group, supergroup, or channel.

:param message_id: Identifier of a message to pin. :param chat_id: Target chat identifier. :param disable_notification: Pin silently without notifying chat members. :return: Status string indicating success.

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

Input Schema

NameRequiredDescriptionDefault
chat_idNo
message_idYes
disable_notificationNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the mutating effect ('Pin a message'), the eligible chat contexts, and the success return ('Status string indicating success'), but it does not mention failure modes, bot permission requirements, or the consequences of pinning over an existing pinned message.

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?

Concept and scope are front-loaded in the first sentence, followed by compact parameter notes and a return note. There is no filler or redundancy.

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

Completeness3/5

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

All three parameters are described and the output schema covers the return type, so the basic call shape is complete. However, for a mutating Telegram tool the description omits the bot's required administrator/pin permission and what happens when chat_id is omitted or null, leaving an agent to discover these from errors.

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 0%, so the description is the only source of parameter meaning. It explains all three parameters, and 'Pin silently without notifying chat members' adds real semantics to disable_notification. The chat_id line is generic ('Target chat identifier') and does not clarify the null/default behavior, but it still identifies the role of the parameter.

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 first sentence states a specific verb ('Pin') and resource ('a message') with an explicit scope ('in a group, supergroup, or channel'). This clearly distinguishes it from siblings such as telegram_unpin_chat_message and telegram_send_message without ambiguity.

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 sentence about groups, supergroups, or channels gives an implicit usage condition, but it does not state when to prefer this tool over siblings, exclude private chats, or mention required permissions. Usage guidance is therefore implied rather than explicit.

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