Skip to main content
Glama

untrash_message

Idempotent

Restore up to 100 messages from the trash back to their original location by specifying one ID or a list of IDs.

Instructions

Take a message (or a list) out of the trash, back where it was. At most 100 items.

Args: messageId: message ID, or a list of IDs.

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": {
      "messageId": "<messageId>"
    },
    "name": "untrash_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.3
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "untrash_messageOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare non-read-only, idempotent, non-destructive, open-world behavior, so the description only needs to add context. It does contribute the 100-item batch cap and 'back where it was' semantics, but says nothing about partial failures, rate limits, or whether original labels/location are fully restored.

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?

Two short sentences, front-loaded with the action and the item cap. The trailing 'Args:' docstring block is slightly redundant, but there is no filler.

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?

For a one-parameter, annotation-covered tool this is close to sufficient; the batch limit and restore semantics are the key facts. Missing is any note on error/partial-failure behavior across a list, which matters most for a bulk operation.

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 0%, so the description carries the burden — and it only restates the schema's anyOf ('message ID, or a list of IDs') without adding format, ID source, or validation detail. Adequate but adds no meaning beyond the schema.

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 description names a specific verb and resource ('take a message ... out of the trash') plus a scope limit of 100 items. It implicitly distinguishes itself from untrash_thread via the 'message (or a list)' wording, though it never names that sibling explicitly.

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?

'Out of the trash, back where it was' implies the precondition that the item is currently trashed, but there is no explicit when-to-use, no mention of untrash_thread for thread-level restores, and no guidance on what happens if an ID was never trashed.

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