Skip to main content
Glama

messages_delete

DestructiveIdempotent

Delete a message from a thread. Supports Telegram, WhatsApp, and other connected channels. Note: Some channels have time limits on message deletion. On an IMAP/SMTP e-mail mailbox the message is MOVED TO THE MAILBOX'S TRASH folder (never erased) and then removed from the inbox here.

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": {
      "thread_id": "<thread_id>",
      "message_id": "<message_id>"
    },
    "name": "messages_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
thread_idYesThread/channel ID containing the message
message_idYesID of the message to delete
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  2. Added
  3. Removed
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds real value beyond that by disclosing channel-dependent time limits and, crucially, that IMAP/SMTP messages are moved to Trash rather than erased. It still does not say what error or result to expect when a time limit is exceeded, nor whether other channel types delete permanently.

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?

Three short sentences, front-loaded with the action and followed by the scope and the important e-mail caveat. The capitalization is slightly noisy but nothing is redundant or padded.

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

Completeness4/5

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

For a destructive mutation with full annotation coverage and no output schema, the description supplies the information an agent most needs: cross-channel applicability, time-limit variability, and the non-destructive e-mail behavior. Only failure semantics for time-limited channels are missing.

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?

With schema description coverage at 100% and only three parameters, the schema already documents thread_id, message_id, and the workspace override. The description adds no parameter-level meaning, so the baseline of 3 applies.

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?

The first sentence gives a specific verb and resource ('Delete a message from a thread'), which is enough to separate it from thread-level tools like threads_delete. However, it never explicitly contrasts with near neighbors such as messages_move or messages_edit, leaving that distinction to be inferred.

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?

Usage context is implied rather than stated: the mention of supported channels and per-channel time limits tells the agent when deletion may fail, but there is no explicit 'use messages_move instead when...' routing or stated prerequisites. The agent must infer when this is the right sibling to pick.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.