Skip to main content
Glama
Sign In
telegram-mcp

telegram-mcp

by dikaglorya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delete a download record

telegram_delete_download

Remove a local downloads-index record by ID, optionally deleting its file. Use it to prune entries whose file is already gone; it does not delete anything on Telegram.

Instructions

Remove one record from the local downloads index by its id, optionally deleting the file it points at. This is local bookkeeping only — nothing is deleted on Telegram. Use it to prune records whose file is already gone (telegram_list_downloads reports exists:false for those).

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": {
      "id": "<id>"
    },
    "name": "telegram_delete_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
deleteFileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

The description adds important behavioral context beyond annotations: the action is local-only and does not affect Telegram, and it may optionally delete the referenced file. It does not explicitly state whether file deletion is irreversible, which is a relevant side-effect detail for a destructive local operation.

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 three compact sentences with no filler. The core action, local-only scope, and primary use case are front-loaded and easy to scan.

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

Completeness5/5

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

For a simple two-parameter local bookkeeping tool with no output schema, the description covers what the tool does, what it does not do, and the main scenario for using it. Nothing essential is missing for correct tool selection.

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?

The description explains the semantic role of both parameters: id identifies the record, and the second option controls deletion of the referenced file. However, it does not highlight the schema default of deleteFile=true, which is important because omitting the parameter still deletes the file.

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 states a specific verb and resource: removing one record from the local downloads index by id, optionally deleting the referenced file. It clearly distinguishes this from Telegram-side deletion and references the related sibling telegram_list_downloads.

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

Usage Guidelines5/5

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

It gives an explicit usage condition: prune records whose file is already gone, identified via telegram_list_downloads reporting exists:false. It also clarifies when-not use by stating this is local bookkeeping only and nothing is deleted on Telegram.

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