Skip to main content
Glama
overpod

MCP Telegram

telegram-delete-stories

Destructive

Delete one or more of your Telegram stories. Requires confirmation as deletion is irreversible.

Instructions

Delete one or more of your own stories. This action is irreversible and requires confirm:true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesStory IDs to delete (1–100 per request)
chatIdNoPeer owning the storiesme
confirmYesPass true to confirm irreversible deletion
Behavior5/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, but the description adds critical behavioral details: 'irreversible' and 'requires confirm:true'. These go beyond annotations, informing the agent of permanent consequences and the mandatory confirmation parameter, which the schema also requires.

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 extremely concise: two sentences that front-load the core action and immediately follow with the critical irreversible+confirm context. Every sentence earns its place with no redundant or verbose phrasing.

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?

Given the low complexity (3 simple params, no output schema, clear annotations), the description covers all key aspects: what it does (delete own stories), behavioral notes (irreversible), and a required confirm flag. It is complete enough for an agent to understand and invoke correctly.

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% with clear descriptions for all three parameters (ids, chatId, confirm). The description only echoes the confirm requirement without adding new semantic meaning. Baseline is 3 because schema already provides full parameter documentation.

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?

Description clearly states 'Delete one or more of your own stories' using a specific verb and resource, distinguishing it from siblings like telegram-delete-message (deletes messages) and telegram-send-story (sends stories). The phrase 'your own stories' clarifies ownership, leaving no 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 description does not explicitly compare this tool to alternatives or provide when-to-use guidance. It implies usage for deleting own stories but lacks statements like 'use instead of telegram-delete-message for stories' or preconditions. The irreversibility warning is helpful but not comparative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/overpod/mcp-telegram'

If you have feedback or need assistance with the MCP directory API, please join our Discord server