Skip to main content
Glama
Mail-MCP

Mail-MCP

by Rixtayz

Permanently delete messages

mail_purge
DestructiveIdempotent

Permanently delete up to 500 messages at once, bypassing Deleted Items so they cannot be restored. Use only when the user explicitly requests permanent deletion.

Instructions

Permanently delete one or more messages (up to 500 ids). This cannot be undone: the messages do not go to Deleted Items and cannot be restored. Only use it when the user explicitly asked for these messages to be deleted permanently; otherwise use mail_delete, which moves them to Deleted Items.

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": {
      "ids": "<ids>"
    },
    "name": "mail_purge"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesMessage ids (1 to 500)

Output Schema

NameRequiredDescriptionDefault
movedNo
failedYes
succeededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.2

TDQS

A4.5/5.0
Behavior4/5

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

The annotation set already declares destructiveHint=true and idempotentHint=true, but the description adds genuinely new behavioral facts: the delete is irreversible, messages bypass Deleted Items entirely, and there is a hard 500-id ceiling. It does not cover partial-failure behavior when some ids are invalid, which keeps it from a 5.

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?

Three short sentences, front-loaded with the action, then the irreversible consequence, then the routing rule — no filler or repetition.

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?

One required parameter, full schema coverage, an output schema for return values, and annotations for safety — nothing an agent needs to call this correctly is missing.

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 coverage is 100% and the single parameter already carries a description plus minItems/maxItems/pattern constraints; the prose only restates the 1-to-500 id cap. Baseline 3 applies since the schema does the heavy lifting.

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 ('Permanently delete one or more messages') plus the scope cap ('up to 500 ids'), and explicitly contrasts itself with the sibling mail_delete, so an agent can distinguish it 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?

Gives an explicit gating condition ('Only use it when the user explicitly asked for these messages to be deleted permanently') and names the alternative (mail_delete) with the behavior that selects it (moves them to Deleted Items).

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