Skip to main content
Glama

gmail trash message

gmail_trash_message
DestructiveIdempotent

Move a Gmail message to Trash so it can be recovered later instead of permanently deleting it.

Instructions

Move a message to Gmail trash (recoverable).

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": {
      "message_id": "<message_id>"
    },
    "name": "gmail_trash_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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, idempotentHint=true, and readOnlyHint=false, so the safety profile is largely covered. The word '(recoverable)' is a genuine addition because destructiveHint=true alone could imply permanence. However, the description says nothing about the side effect that matters most operationally — that the message leaves the inbox and moves to the Trash label.

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?

One short sentence, front-loaded with the action and destination, with the recoverability caveat placed where it is immediately visible. Nothing is padded or redundant.

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?

The tool is a simple one-parameter mutation with rich annotations and an output schema, so return values need not be described. The remaining gap is the absence of any guidance on trash versus permanent delete, which is a minor omission for a low-complexity tool.

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?

Schema description coverage is 0%, so the description carries the burden and adds no meaning for message_id. In practice the single required parameter has a self-explanatory name ('Message Id' title), so the practical ambiguity is low even though the description contributes nothing.

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 ('Move') with a specific resource ('a message') and destination ('Gmail trash'), so the operation is unmistakable. It does not name a contrasting sibling (e.g., permanent delete or drive_trash_file), but the resource prefix 'Gmail' already separates it from the Drive trash tool.

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 statement of when to use this versus a permanent-delete path or a label-modification approach; the only hint is the parenthetical '(recoverable)'. An agent must infer that trash is the non-destructive removal option from that single word.

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