Skip to main content
Glama
Sign In
Mail-MCP

Mail-MCP

by Rixtayz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delete messages

mail_delete
DestructiveIdempotent

Delete one or more emails by ID. Moves to Deleted Items unless permanent deletion is specified.

Instructions

Delete one or more messages (up to 500 ids). By default messages go to Deleted Items (recoverable with mail_search folder=deleteditems then mail_move; their id changes). permanent: true deletes irreversibly: only use it when the user explicitly asks for it.

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_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesMessage ids (1 to 500)
permanentNotrue = permanent deletion (irreversible). Default: Deleted Items.

Output Schema

NameRequiredDescriptionDefault
movedNo
failedYes
succeededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Discloses the irreversible nature of permanent deletion and the recoverability of default deletion. Annotations already mark destructive and idempotent, but the description adds concrete details about the default behavior and recovery path.

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 concise sentences, each packed with essential information. No redundant words or unnecessary details.

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?

Given the tool's complexity, it covers all key aspects: action, limits, default vs permanent behavior, recovery, and idempotency. The output schema exists but is not needed for the description to be complete.

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

Parameters5/5

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

Schema descriptions cover both ids and permanent with constraints. The description reinforces these by explaining the effect of permanent and the recovery mechanism, adding value beyond the schema.

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?

Clearly states the action (delete) and the resource (messages), with a specific limit of up to 500 ids. It implicitly distinguishes from sibling tools like mail_move and mail_search.

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 explains the default behavior (move to Deleted Items) versus permanent deletion, and notes recovery via mail_search and mail_move. It also instructs to use permanent only when explicitly requested, providing clear usage guidance.

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