proton-mail-mcp

Overview Schema Source Related Servers Discussions Admin

delete_thread

Destructive

Delete an entire email thread by providing a Message-ID. Choose between soft-delete (Trash) or permanent deletion, with optional cross-folder and dry-run modes.

Instructions

Delete every message in a thread. Default soft-deletes to Trash; permanent:true expunges. acrossFolders:false by default for safety. dryRun:true previews.

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": {
      "messageId": "<messageId>"
    },
    "name": "delete_thread"
  }
}

Input Schema

Name	Required	Description
`messageId`	Yes	RFC 5322 Message-ID of any message in the thread (e.g. `<abc@example.com>`); the whole reply chain is resolved from it.
`permanent`	No	When false (default), soft-delete the thread to Trash (recoverable). When true, permanently expunge every message — irreversible.
`acrossFolders`	No	When false (default), act only within the seed message's folder. When true, walk INBOX + Sent + All Mail so the whole conversation is deleted across folders.
`dryRun`	No	When true, preview which messages would be deleted (per folder) without deleting anything. Recommended before a real run.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.0.2May 30, 2026

addedInput schema / properties / acrossFolders / description

Added value: +"When false (default), act only within the seed message's folder. When true, walk INBOX + Sent + All Mail so the whole conversation is deleted across folders."

addedInput schema / properties / dryRun / description

Added value: +"When true, preview which messages would be deleted (per folder) without deleting anything. Recommended before a real run."

addedInput schema / properties / messageId / description

Added value: +"RFC 5322 Message-ID of any message in the thread (e.g. `<abc@example.com>`); the whole reply chain is resolved from it."

addedInput schema / properties / permanent / description

Added value: +"When false (default), soft-delete the thread to Trash (recoverable). When true, permanently expunge every message — irreversible."

First observedv1.0.1May 30, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already mark destructiveHint=true. Description adds essential details: default soft-delete to Trash, permanent expunge irreversibility, folder-scoping safety defaults, and dry-run preview. This goes well beyond the annotation and fully discloses behavioral traits.

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 front-load the core action and immediately provide key behavioral nuances. Every sentence adds value with no redundancy.

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 destructive thread operation, description covers behavior, scope, preview, and safety defaults. No output schema needed; return values are implied. Complete enough for an agent to invoke correctly.

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?

Input schema covers all 4 parameters with descriptions (100% coverage). The description adds minimal extra meaning beyond schema (e.g., 'for safety', 'previews'), but baseline is 3 due to high schema coverage. No new constraints or clarifications added.

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 clearly states the tool deletes every message in a thread (specific verb+resource). It distinguishes from siblings like delete_message (single message) and bulk_delete (multiple arbitrary messages) by focusing on thread-level deletion.

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?

Description provides clear context on default behavior (soft-delete), irreversible option (permanent), scope control (acrossFolders), and preview mode (dryRun). Although not explicitly stating when to use vs alternatives, the parameter guidance strongly implies proper usage scenarios.

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