Skip to main content
Glama
Sign In
telegram-mcp

telegram-mcp

by dikaglorya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Unpin every message

telegram_unpin_all

Remove all pinned messages from a Telegram chat in a single call. Clear a chat's pinned message list without manual unpinning.

Instructions

Remove all pinned messages from a chat in one call.

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": "<chat>"
    },
    "name": "telegram_unpin_all"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the agent knows this is a mutation affecting external state. The description adds the specific effect (removing all pinned messages) but doesn't mention required permissions, reversibility, or other behavioral details.

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?

A single, front-loaded sentence with zero waste. It efficiently conveys the core action and scope.

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?

For a simple mutation tool with one parameter and some annotation coverage, the description covers the basic action but leaves gaps in parameter format and operational details like permissions or side effects. It is minimally adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description only says 'from a chat' without explaining the 'chat' parameter's format (e.g., username, ID, or link). It fails to compensate for the lack of schema documentation.

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 states a specific verb 'Remove all pinned messages' and resource 'from a chat', making the tool's effect clear. It distinguishes itself from single-message pinning siblings like telegram_pin_message, though it doesn't explicitly name alternatives.

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 phrase 'in one call' implies this is a batch operation, hinting at when to use it over unpinning individually. However, it does not explicitly state when to use this versus alternatives or any prerequisites.

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