Skip to main content
Glama
gmail-mcp
by gchallen

trash_thread

Destructive

Move all messages in a Gmail thread to Trash to clear an entire conversation at once.

Instructions

Move every message in a thread to 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": "trash_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
threadIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety is covered. The description adds meaningful scope detail — the operation applies to ALL messages in the thread, not one — but omits whether the move is recoverable via untrash_thread and whether any permissions are required.

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 no filler; the key scope qualifier ('every message') appears early. Nothing to trim, though it could have used its brevity budget to add one sentence of guidance.

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 destructive mutation with no output schema and an undocumented parameter, the definition covers purpose and blast radius but leaves out recoverability, permissions, and parameter meaning. Adequate minimum, with clear gaps.

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?

With one required parameter at 0% schema description coverage, the description should clarify what identifies the thread. It only implies a thread identifier via 'in a thread' and adds no format or source information beyond that inference.

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 ('Move ... to Trash') and resource scope ('every message in a thread'), which distinguishes it from the sibling trash_message that operates on a single message. Clear, though it doesn't explicitly name the message-level alternative.

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?

The phrase 'every message in a thread' implies this is the thread-level variant, but there is no explicit when-to-use vs trash_message guidance, no mention of untrash_thread as the recovery path, and no preconditions stated.

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