proton-mail-mcp

Overview Schema Source Related Servers Discussions Admin

bulk_move

DestructiveIdempotent

Move multiple emails to a folder at once using explicit UIDs or search criteria, with a dry-run option to preview changes.

Instructions

Move multiple messages to a different folder in one operation. Provide EITHER uids (an explicit list) OR match (search criteria — same shape as search_messages), not both. Set dryRun: true to preview what would be moved without making changes. Note: moved messages get new UIDs in the destination folder.

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

Input Schema

Name	Required	Description	Default
`folder`	No	Source folder (default: INBOX)	INBOX
`uids`	No	Explicit UIDs to move (mutually exclusive with `match`)
`match`	No	Search criteria; matching messages will be moved (mutually exclusive with `uids`)
`destination`	Yes	Destination folder path
`dryRun`	No	If true, preview without moving

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?

Beyond annotations (destructiveHint, idempotentHint), the description warns that moved messages get new UIDs in the destination and explains dryRun behavior. No contradiction with annotations.

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, each essential, front-loaded with purpose, no filler. Well-structured for quick comprehension.

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

Completeness4/5

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

Given no output schema and moderate complexity (5 params, nested objects), the description covers key aspects: parameter mutual exclusivity, dryRun, and UID renumbering. Lacks output return info, but is still fairly complete.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. Description adds value by clarifying the mutual exclusivity of uids and match, and explaining dryRun effect, which goes beyond the schema descriptions.

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 'Move multiple messages to a different folder,' specifying the verb and resource. It distinguishes itself from siblings like move_message and move_thread by indicating batch operation, and mentions the two mutually exclusive parameter options.

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 explains when to use uids vs match, and introduces dryRun for preview. However, it does not provide guidance on when to prefer this tool over alternatives like bulk_delete or move_message, leaving some ambiguity.

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