Skip to main content
Glama
gmail-mcp
by gchallen

untrash_message

Restore one Gmail message from Trash using its message ID, moving it out of Trash so it can be accessed again.

Instructions

Restore one message from Trash.

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. First observedv2026.9.2

TDQS

B3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is largely covered. The description adds only the state precondition that the target must be in Trash; it says nothing about required permissions, error behavior for non-trashed messages, or whether the restored message returns to its original labels.

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?

A single front-loaded sentence with zero filler; the verb and scope appear immediately. It is efficient, though so terse that the brevity shades into under-specification rather than pure conciseness.

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, non-destructive restore operation with annotations present and no output schema, the description covers the core action adequately. It leaves the parameter's expected form and failure conditions unaddressed, which is a modest but real gap.

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% for the single messageId parameter, so the description carries the burden — but "one message" only implies a single-message identifier without specifying format, source, or whether it accepts a bare ID versus a prefixed one. This is a clear gap relative to the low schema coverage.

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 pairs a specific verb ("Restore") with a specific resource and scope ("one message from Trash"), which clearly separates it from the thread-level sibling untrash_thread and from trash_message. It stops short of naming any sibling explicitly, so it is clear but not maximally differentiating.

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 is only implied by the phrase "from Trash" — an agent can infer the tool applies to a message currently in Trash and that it is the inverse of trash_message. There is no explicit when-to-use statement, no exclusion (e.g. use untrash_thread for whole threads), and no mention of behavior when the message is not in Trash.

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