Skip to main content
Glama
gmail-mcp
by gchallen

untrash_thread

Restore all messages in a Gmail thread from Trash using its thread ID to bring deleted conversations back to the inbox.

Instructions

Restore every message in a thread 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": {
      "threadId": "<threadId>"
    },
    "name": "untrash_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
threadIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

B3.4/5.0
Behavior3/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 covered. The description adds useful behavioral detail beyond that: the operation is a bulk restore affecting every message in the thread and pulls them out of Trash. It does not say what happens if some messages were never trashed, whether it is idempotent, or what permissions are needed.

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?

One short sentence, front-loaded with the verb and scope, with no filler or redundancy.

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 simple one-parameter restore tool with annotations covering risk and no output schema, the description is nearly sufficient. The remaining gap is failure/idempotency behavior when the thread or its messages are not in Trash.

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 one required parameter (threadId) at 0% schema description coverage, the description's phrase "a thread" implies the identifier is a thread, which is the bare minimum needed. It adds no format, example, or constraint detail, but for a single obvious identifier the gap is small.

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 states a specific verb ("Restore") and a precise scope ("every message in a thread") plus the source state ("from Trash"). That scope wording implicitly separates it from untrash_message, which operates on a single message, though no sibling is named outright.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to pick this over untrash_message or trash_thread; the agent must infer the choice from the word "thread" versus "message." No prerequisites (e.g., the thread must currently be in Trash) are stated.

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