Skip to main content
Glama
Sign In
ProtonMail MCP Server

ProtonMail MCP Server

by ronamosa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delete_email

Destructive

Move emails to Trash, or permanently delete them if already in Trash.

Instructions

Delete an email. Moves to Trash first; permanently deletes only if already in Trash.

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

Input Schema

NameRequiredDescriptionDefault
emailIdYesEmail ID (format: folder:uid)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate destructiveHint, so the description adds value by detailing the two-step deletion process (Trash first, then permanent). This goes beyond the annotations without contradicting them.

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 sentences, no wasted words, front-loaded with the action. Every sentence provides distinct information, making it highly concise.

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 tool with one required parameter, good annotations, and no output schema, the description fully covers behavior and edge cases. No additional context needed.

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% for the single parameter emailId, which already includes description. The tool description does not add additional meaning beyond what the schema provides, so 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 explicitly states 'Delete an email' and distinguishes the two-step behavior (moves to Trash first, permanently deletes only if already in Trash). This is specific and differentiates from siblings like delete_draft or move_email.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use it (for deletion, with awareness of current state), but does not explicitly compare to alternatives like move_email or delete_draft. The two-step process gives some context but lacks explicit when-to-use 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