Skip to main content
Glama

trash_thread

Idempotent

Move a Gmail thread or list of threads to the trash without confirmation; items are reversible for 30 days and never permanently deleted by this tool.

Instructions

Move a whole thread (or a list) to the trash, no confirmation needed: reversible for 30 days (untrash_thread).

After 30 days Gmail deletes it for good. This tool never deletes for good nor empties the trash. At most 100 items.

Args: threadId: thread 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": {
      "threadId": "<threadId>"
    },
    "name": "trash_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
threadIdYes

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": "trash_threadOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations say destructiveHint=false and idempotentHint=true; the description supplies the reason (30-day soft delete, then Gmail purges) and rules out the permanent-delete behavior an agent might otherwise assume from 'trash'. That is genuine added context. It does not address permissions or partial-failure behavior on a 100-item batch, so not a 5.

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?

The reversibility window and the 'never deletes for good' boundary are front-loaded, with the batch cap and arg note following. Every sentence adds a distinct constraint; nothing repeats the annotations verbatim.

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?

One required param, no output schema, and annotations present, so the remaining burden is light and mostly met: reversibility, purge timing, non-destructive scope, and batch limit are all covered. Partial-batch failure and return shape are unaddressed, which is the only real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter, and it does: 'threadId: thread ID, or a list of IDs' explains the string-or-array union in the schema. It stops short of ID format or encoding details, leaving a small gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Move a whole thread (or a list) to the trash'), including the batch capability that the name alone does not convey. The thread-vs-message distinction is clear enough to separate it from trash_message without opening either schema.

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

Usage Guidelines5/5

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

Explicitly says no confirmation is needed, names the reversal path (untrash_thread), and sets a negative boundary: 'This tool never deletes for good nor empties the trash.' It also caps batch size at 100, so an agent knows both when to call it and when it must split work.

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