proton-mcp

Overview Schema Source Related Servers Discussions Admin

Move messages to the trash

trash_messages

Idempotent

Move messages to Trash to remove them from their mailbox while keeping deletion reversible; recover them later by moving them back out.

Instructions

Moves messages to the trash. This is what deletion means here: the messages stay in "Trash" and in "All Mail" and can be moved back out with move_messages. There is no tool in this server that deletes a message for good or empties the trash, so that a wrong decision stays reversible.

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": {
      "messageIds": "<messageIds>"
    },
    "name": "trash_messages"
  }
}

Input Schema

Name	Required	Description	Default
`mailbox`	No	The mailbox the messages are in, if they share one. Only a shortcut: without it every message is looked for across the mailboxes it could be in, which costs a request each.
`messageIds`	Yes	The message ids, as they came from a listing or a search. At most 50 per call.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.11Nov 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes beyond the annotations by explaining why destructiveHint is false: messages remain in Trash and All Mail, can be moved back out, and no permanent deletion exists. This adds valuable reversibility and retention context that the annotations alone do not convey.

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 tight sentences front-load the action and then add only the behavioral context needed to use it safely. No redundancy or filler.

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 two-parameter mutation with rich schema descriptions and annotations covering safety and idempotency, the description supplies the missing behavioral context: reversibility, retention, and the absence of permanent deletion. An agent has everything needed to call it 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?

Schema description coverage is 100%, so both parameters (mailbox and messageIds) are fully documented in the schema. The description adds no parameter-level detail, which is acceptable given the high coverage but does not exceed the baseline.

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 ('Moves messages to the trash') and immediately distinguishes this action from move_messages and from permanent deletion. An agent can tell exactly what this tool does and what it does not do.

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 frames this as the deletion action ('This is what deletion means here'), names move_messages as the way to restore messages, and states that no permanent-delete or empty-trash tool exists. This gives clear when-to-use and when-not-to-look-elsewhere guidance.

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