Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

delete_email

Deletes one or more emails by UID, moving them to trash by default or permanently removing them when permanence is requested. Handles single or multiple messages in any folder.

Instructions

Delete one or more messages (uids = a single uid OR a list), by default into the trash.

permanent=True deletes for good instead of moving to the trash - cannot be undone, only use with explicit confirmation.

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": {
      "uids": "<uids>"
    },
    "name": "delete_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidsYes
folderNoINBOX
permanentNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and discloses the critical distinction between trash deletion and irreversible permanent deletion. It states that permanent deletion cannot be undone and requires explicit confirmation, though it does not address permissions or error behavior.

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 short and front-loaded, stating the core action first and the destructive permanent option immediately after. Every sentence adds necessary deletion semantics without repetition.

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

Completeness4/5

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

For a destructive mutation tool with no annotations, the description covers the essential safety behavior and permanent-delete semantics. An output schema exists, so return-value explanation is unnecessary, but the folder parameter remains undocumented in the description.

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 0%, so the description must compensate. It explains that uids can be a single integer or a list and clearly defines permanent=True, but it does not explain the folder parameter or its INBOX default.

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 uses a specific verb and resource: delete one or more messages identified by uid. It also distinguishes deletion behavior by saying messages go to trash by default or are permanently deleted with permanent=True.

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 gives clear operational context: default deletion moves to trash, and permanent=True should only be used with explicit confirmation. It does not name alternative tools such as move_email, but the permanent-delete condition is explicit.

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