Skip to main content
Glama
gmail-mcp
by gchallen

trash_message

Destructive

Move a single Gmail message or draft to Trash by message ID. For entire conversations, use a thread-level trash action instead.

Instructions

Move one message to Trash (also works on a draft's message ID). Prefer trash_thread for whole conversations.

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. First observedv2026.9.2

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real behavioral nuance beyond that: the operation targets Trash (implying recoverability rather than permanent deletion) and accepts draft message IDs, which annotations cannot express. It stops short of saying how to restore the message or what happens if it is already trashed.

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?

Two compact sentences with zero filler, and the primary action is front-loaded before the sibling reference. Every clause carries decision-relevant information.

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 one-parameter mutation with full annotation coverage and no output schema, the description supplies scope, the alternative tool, and the ID nuance. Only restore-path and already-trashed behavior are unaddressed, which are minor for this complexity.

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 coverage is 0%, so the single messageId parameter is otherwise undocumented. The description compensates by telling the agent the ID must identify one message and may also be a draft's message ID, which is exactly the ambiguity an agent would hit here.

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 one message to Trash') and immediately bounds the scope to a single message, which separates it from trash_thread by name. An agent can pick between the two 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 routes whole-conversation work to trash_thread, so the alternative and the condition that selects it are both stated. It also clarifies that a draft's message ID is a valid target, removing the most likely usage doubt.

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