Skip to main content
Glama

delete_message

DestructiveIdempotent

Delete a message for everyone after confirming with the user. Use the chat and message ID to remove an existing message from team chat.

Instructions

Delete one of my messages for everyone. 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": {
      "chat": "<chat>",
      "message_id": "<message_id>"
    },
    "name": "delete_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes
message_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already flag destructive=true, idempotent=true, and openWorld=true, so the safety profile is covered. The description still adds value by disclosing the blast radius ('for everyone', not just local visibility) and a required confirmation step before execution — context the annotations do not convey.

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?

Two short sentences, both front-loaded with the highest-value information: the irreversible scope first, the required confirmation second. Zero waste.

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?

With an output schema present, return values need not be explained, and the destructive semantics are well covered. The remaining gap is parameter format guidance, which matters because the schema supplies no descriptions at all.

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%, so the description carries the full burden for two required parameters. It implies the targeting ('one of my messages') but never explains whether 'chat' expects an ID, name, or handle, nor the message_id format — the main ambiguity an agent will hit.

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 specific verb and resource ('Delete one of my messages') plus a crucial scope qualifier ('for everyone'), which distinguishes it from a self-only delete or edit_message. It stops short of naming a sibling, but the operation is unambiguous.

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?

'Confirm with the user first' is a real usage directive that shapes invocation behavior, so this is better than no guidance. However, it gives no when-not conditions (e.g., when to use edit_message instead) and no prerequisites such as ownership or permission scope beyond 'my messages'.

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