Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gmail: Trash message

gmail_trash_message
Destructive

Move a Gmail message to trash so it can be recovered for about 30 days. Use site and message_id to target the specific message.

Instructions

[UNIFIED] Move a Gmail message to trash. Recoverable until ~30 days.

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

Input Schema

NameRequiredDescriptionDefault
siteYes
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.2/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 known. The description adds genuinely new context: the action is 'Recoverable until ~30 days,' which tells the agent the operation is reversible within a retention window. It leaves gaps on edge cases (already-trashed messages, what happens to existing labels) and on the non-idempotent behavior flagged by annotations.

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?

Two short sentences, front-loaded with the action and followed by the retention caveat. The only waste is the unexplained "[UNIFIED]" prefix, which consumes attention without conveying meaning.

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 two-parameter mutation with no output schema, the description covers the core action and its reversibility. It is incomplete on the undocumented 'site' parameter and on the non-idempotent semantics that annotations raise but do not explain (e.g., what a repeated trash call returns).

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?

Schema description coverage is 0% with two required parameters. 'message_id' is loosely inferable from 'a Gmail message,' but 'site' is completely undocumented in both schema and description — the agent cannot tell whether it is an account, workspace, or Gmail host selector.

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 states a specific verb and resource: "Move a Gmail message to trash." That is unambiguous and an agent can immediately distinguish it from read-oriented siblings like gmail_get_message. It stops short of naming the inverse operation (gmail_untrash_message) or clarifying the unexplained "[UNIFIED]" prefix.

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 when-to-use or when-not-to-use guidance, no mention of gmail_untrash_message as the recovery path, and no prerequisites such as whether the message must currently be in the inbox. Usage is only implied by the verb 'Move ... to trash'.

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

Deploy Server

Other Tools