Skip to main content
Glama
Sign In
telegram-bot-mcp

telegram-bot-mcp

by FantomaSkaRus1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

pin_message

Pin a message to a chat using its ID. Optionally set the target chat or disable notification.

Instructions

Pin a message in a chat. Bot must have pin permissions. If chat_id is omitted, targets the default log group.

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": "pin_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idNoChat ID or @channel_username. Optional — defaults to log group
message_idYesID of the message to pin
disable_notificationNoPin silently without notification

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.3

TDQS

A3.8/5.0
Behavior3/5

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

The description discloses required permissions and default chat behavior, but lacks details on side effects (e.g., what happens if message is already pinned, limits on pinned messages, or notification impacts of disable_notification). With no annotations, the description carries full burden and falls short.

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 two sentences, front-loaded with the action, and includes necessary context without extraneous detail. 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 the tool's low complexity (3 parameters, no output schema), the description covers core aspects: purpose, permissions, and default. It lacks mention of return behavior (success/failure) but is otherwise adequate for a simple pin tool.

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?

Schema coverage is 100%, so the schema already provides descriptions for all parameters. The description adds no new parameter meaning beyond repeating the default chat_id behavior. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Pin a message') and resource ('in a chat'), with additional context about permissions and default chat behavior. It effectively communicates the core purpose, though it could be more explicit in distinguishing from sibling tools like unpin_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 clear guidance on prerequisites ('Bot must have pin permissions') and default behavior when chat_id is omitted. However, it does not explicitly mention when not to use this tool or point to alternatives for unpinning.

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