proton-mail-mcp

Overview Schema Source Related Servers Discussions Admin

move_message

DestructiveIdempotent

Move an email message to a specified destination folder such as Archive, Trash, or Spam. Provide the message UID and source folder.

Instructions

Move an email message to a different folder. Note: the message gets a new UID in the destination folder — the original UID is no longer valid after the move.

UID + folder pair caveat: IMAP UIDs are per-folder, so UID 42 in INBOX and UID 42 in Sent identify different messages. Always carry the folder a UID came from; never reuse a UID across folders. For thread-level operations on messages you only know by Message-ID, prefer get_thread / move_thread which sidestep this footgun.

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": {
      "uid": "<uid>",
      "destination": "<destination>"
    },
    "name": "move_message"
  }
}

Input Schema

Name	Required	Description	Default
`uid`	Yes	Message UID (use list_messages or search_messages to find UIDs)
`folder`	No	Source folder (default: INBOX)	INBOX
`destination`	Yes	Destination folder path (e.g. Archive, Trash, Spam)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1May 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Disclosures that the message gets a new UID and that original UID becomes invalid, plus the per-folder UID caveat. Adds significant behavioral context beyond annotations (destructiveHint) by explaining what changes irreversibly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two clear paragraphs: first states action and immediate effect, second explains UID caveat. Could be slightly more concise (e.g., second paragraph is explanatory but not wasteful). Good front-loading.

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?

Despite no output schema, the description explains result (new UID, old invalid) and provides essential caveats for safe usage. Covers what changes and how UIDs behave, making it complete for a move operation.

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%, and each parameter has a description in the schema. The description adds no additional parameter-level detail beyond what's in the schema, so baseline score of 3 applies.

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?

Explicitly states 'Move an email message to a different folder', clearly specifying the verb (move) and resource (email message). Distinguishes from siblings like delete_message or copy operations by focusing on move behavior.

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?

Provides explicit when-to-use context (moving a single message) and warns about UID invalidity. Also directly recommends alternatives for thread-level operations: 'prefer get_thread / move_thread', giving clear direction.

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