Skip to main content
Glama

Delete a message

delete_message
DestructiveIdempotent

Permanently unsend a chat message, for everyone when the network allows or only for you, using its chat ID and final message ID.

Instructions

Delete (unsend) a message. By default it is deleted for everyone when the network allows it (usually only your own, recent messages). Needs the final message ID: a pendingMessageID from send_file only becomes deletable once the message is sent. This cannot be undone: confirm with the user first.

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": {
      "chatID": "<chatID>",
      "messageID": "<messageID>"
    },
    "name": "delete_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatIDYesChat ID (or local chat ID)
messageIDYesID of the message to delete
forEveryoneNotrue (default): delete for everyone; false: only for you, when supported

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already mark the tool destructive, open-world, and idempotent, but the description adds critical context: deletion cannot be undone, default behavior is delete-for-everyone when the network allows it, and usually only recent own messages qualify. It also explains the pendingMessageID caveat from send_file, which is exactly the sort of behavioral detail an agent needs before invoking a destructive tool.

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 tightly written sentences with the core operation, scope constraints, ID requirement, and irreversibility front-loaded. Every sentence earns its place, and there is no redundant restatement of the tool name.

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 destructive mutation tool with full schema coverage and annotations covering safety traits, the description supplies the remaining critical context: irreversibility, confirmation guidance, default audience scope, network limitations, and the pending-message caveat. No output schema exists, so there is no missing return-value explanation.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining that messageID must be the final message ID and that a pendingMessageID is not deletable until the message is sent. It also reinforces the default behavior of forEveryone, though the schema already documents that parameter.

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: “Delete (unsend) a message.” It also clarifies the default scope, deleting for everyone when supported, which distinguishes the operation from merely hiding or editing a 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?

It gives practical conditions: deletion for everyone usually works only for your own recent messages, and the tool requires a final message ID. It also advises confirming with the user first, though it does not explicitly name sibling alternatives such as edit_message.

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