Skip to main content
Glama
Sign In
gmail-multi-mcp

gmail-multi-mcp

by blackwings-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Move an email to the bin

trash_email
DestructiveIdempotent

Move an email to the Gmail bin without permanent deletion. Restore it within 30 days using untrash_email; after that, Gmail deletes it automatically.

Instructions

Move a message to the bin. This is NOT a permanent delete: the message keeps existing and untrash_email brings it back. Gmail does empty the bin by itself after 30 days, so it becomes permanent eventually — treat it as reversible for a month, not for ever. This server has no permanent-delete tool at all. The answer names the message that moved, so a wrong id is visible immediately.

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": "trash_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYesConfigured account: the email address, or the alias given at setup.
message_idYesMessage to move to the bin.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already provide readOnlyHint=false and destructiveHint=true, but the description adds significant behavior beyond that: it is not permanent, the message stays existing, untrash_email can restore it, Gmail auto-empties after 30 days, and a wrong ID is visible in the response. This gives the agent a much richer model of the tool's side effects.

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 core action and then adds only high-value caveats: reversibility, the 30-day limit, absence of permanent delete, and response feedback. No sentence is wasted, and the structure is easy to scan.

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 simple two-parameter tool with no output schema, the description covers everything needed: what the tool does, its side effects, how to undo it, and what to look for in the response. It also addresses the relevant sibling untrash_email and the lack of a permanent-delete alternative.

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 100%, so the schema already documents both parameters ('Configured account' and 'Message to move to the bin'). The description adds little beyond naming the bin, so the baseline of 3 is appropriate.

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 opens with a specific action and resource: 'Move a message to the bin.' It distinguishes this from a permanent delete and from recovery via untrash_email, so an agent can immediately tell what the tool is for and how it differs from related actions.

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?

The description makes the usage context clear by explaining that this is reversible for 30 days and that no permanent-delete tool exists. It doesn't literally say 'use this when you want to soft-delete and use untrash_email to undo,' but that is strongly implied by the contrast with untrash_email and the warning about Gmail's 30-day emptying.

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