Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

move_email

Moves one or more messages from a source folder, defaulting to INBOX, into a destination folder and removes them from the source to organize mail.

Instructions

Move one or more messages (uids = a single uid OR a list) to another folder.

Removes the message from the source folder (src_folder, default INBOX). To
only set a label (the message stays in the inbox): add_label.

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>",
      "dest_folder": "<dest_folder>"
    },
    "name": "move_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidsYes
src_folderNoINBOX
dest_folderYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the key consequence that the message is removed from the source folder and that src_folder defaults to INBOX. It omits whether dest_folder must pre-exist, what happens to non-existent uids/folders, and whether the whole batch is atomic on partial failure.

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?

Three short lines, front-loaded with the action and the uid shape, then the side effect, then the escape hatch to add_label. No filler; only minor redundancy with the schema's defaults.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the core mutation behavior is stated. For a destructive-move tool with zero annotation coverage, though, the definition leaves folder-targeting semantics and failure behavior undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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, but it mostly restates what the schema already shows: the anyOf already conveys single-uid-or-list and the default INBOX is declared in the schema. It adds no clarity on what form dest_folder takes (folder name vs. path vs. ID), which is the parameter most likely to be mis-supplied.

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?

Specific verb plus resource ("Move one or more messages ... to another folder") with explicit scope ("one or more", uids accept a scalar or a list). It also distinguishes itself from add_label by contrasting move-with-removal against label-only.

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?

Explicitly routes the label-only case to add_label ("To only set a label (the message stays in the inbox): add_label"), which is the most likely confusion point. It does not, however, contrast with delete_email or copy-like alternatives, so guidance is clear but not exhaustive.

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