Skip to main content
Glama
Sign In
google-workspace-mcp

google-workspace-mcp

by smk-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

gmail_message_trash

Move a Gmail message to Trash to remove it from the inbox while keeping it recoverable for 30 days. Use with an account and message ID to perform the action.

Instructions

Move a message to Trash (reversible for 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": {
      "account": "<account>",
      "message_id": "<message_id>"
    },
    "name": "gmail_message_trash"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYes
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.2

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses reversibility and duration, but omits details like required permissions, thread-level effects, or the behavior if the message is already trashed. This is adequate but not thorough for a mutation action.

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?

Single sentence with no wasted words. It is front-loaded with the core action and includes a parenthetical qualifier for reversibility. Perfectly concise.

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

Completeness2/5

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

Given no output schema, no annotation coverage, and minimal description, the tool is under-documented. The agent lacks information about return values, error conditions, or handling of edge cases (e.g., message already in trash). Requires significant inference.

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

Parameters1/5

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

Schema description coverage is 0%, meaning neither the schema nor the description explains the parameters. The description does not mention 'account' or 'message_id', leaving the agent to guess their meaning. This severely undermines correct invocation.

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 clearly states the action ('Move a message to Trash') and includes a key behavioral detail (reversible for 30 days). It effectively distinguishes from sibling tools like gmail_message_get (read-only) and gmail_send (send email).

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?

The description provides no guidance on when to use this tool vs alternatives (e.g., permanent deletion, archiving). It does not mention prerequisites or constraints beyond the 30-day reversibility, leaving the agent to infer appropriate use cases.

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