Skip to main content
Glama
Sign In
telegram-mcp

telegram-mcp

by dikaglorya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Clear a chat's history

telegram_clear_history
Destructive

Delete messages from a Telegram chat, either only from your copy or for everyone when revoke is enabled and you have permission.

Instructions

Delete messages from a chat. Defaults to your own copy only (revoke=false). revoke=true also removes them for everyone, which needs the rights to do so. Returns the message count Telegram reports as affected when it says.

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_clear_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes
maxIdNo
revokeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true. The description adds valuable context beyond annotations: default revoke=false deletes only your own copy, revoke=true removes messages for everyone and requires rights to do so, and it returns a message count from Telegram. This covers permission needs, deletion scope, and return behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three concise sentences, front-loaded with purpose then behavior. Every sentence adds information, though the final sentence about the return value is slightly awkwardly phrased. No unnecessary filler.

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 3-parameter mutation tool with no output schema, the description covers deletion scope, permission requirements, and return value. However, it omits explanation of the maxId parameter and does not clarify how this differs from telegram_delete_messages, leaving gaps for correct invocation.

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 coverage is 0%, so the description must compensate. It explains the revoke parameter well (default false, true removes for everyone, needs rights), but leaves the maxId parameter completely undocumented and only implicitly covers 'chat'. Partial compensation warrants a low score.

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?

States a clear verb and resource: 'Delete messages from a chat.' However, it does not differentiate this tool from sibling telegram_delete_messages, which appears to delete individual messages rather than clear an entire chat history. The tool name suggests scope, but the description alone is slightly ambiguous.

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

Usage Guidelines2/5

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

The description explains the revoke parameter's effect but gives no guidance on when to use this tool versus alternatives like telegram_delete_messages or telegram_delete_chat. No when-to-use or when-not-to-use conditions are provided.

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