Skip to main content
Glama

trash_message

Idempotent

Move one or more Gmail messages to trash without confirmation, with restore available for 30 days. It does not permanently delete messages or empty the trash.

Instructions

Move a message (or a list) to the trash, no confirmation needed: reversible for 30 days (untrash_message).

After 30 days Gmail deletes it for good. This tool never deletes for good nor empties the trash. 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": "trash_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": "trash_messageOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already state this is non-read-only, idempotent, open-world, and not destructive. The description adds critical behavior beyond them: the 30-day reversibility window, Gmail's eventual permanent deletion, the fact that this tool never permanently deletes or empties trash, and the 100-item limit.

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 description is front-loaded with the action and key reversibility guarantee, then adds the permanence caveat and limit. Every sentence contributes operational information, and the Args section is compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter mutation tool with no output schema, the description covers the essential behavior: reversibility, eventual permanence, non-destructive scope, limits, and the sibling tool for undo. Nothing needed to invoke it correctly appears to be missing.

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 explain the single parameter. It clarifies that messageId can be a single ID or a list of IDs and that at most 100 items are allowed, which adds meaning beyond the schema's anyOf union.

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?

The description states a specific verb and resource: moving a message, or a list of messages, to the trash. It also names the sibling tool for reversal, untrash_message, and makes clear this is not thread trashing.

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

Usage Guidelines4/5

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

It gives clear context for use: no confirmation is needed, the action is reversible for 30 days, and at most 100 items can be passed. It names untrash_message as the reversal path but does not explicitly compare against trash_thread for thread-level trashing.

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