Skip to main content
Glama
Sign In
proton-mcp

proton-mcp

by RndmJoker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Move messages to a folder

move_messages
Idempotent

Moves up to 50 messages to an existing Proton Mail folder, removing them from their current folder while preserving labels. Use folders only; apply labels with add_label instead.

Instructions

Moves messages into a folder. In Proton a message lives in exactly one folder, so this takes it out of the one it is in. Labels are not affected and survive the move. Only folders are valid destinations: moving into a label would apply the label and leave the message where it is, so a label is refused here and add_label does that job. The destination has to exist; this server does not create folders.

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>",
      "target": "<target>"
    },
    "name": "move_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesThe destination folder, for example "Archive" or "Folders/Work". Use list_folders to see the paths. Note that Proton fills the inbox through delivery: a message moved to "INBOX" over IMAP was measured to end up elsewhere shortly afterwards.
mailboxNoThe 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.
messageIdsYesThe message ids, as they came from a listing or a search. At most 50 per call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.11

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, and the description adds non-obvious behavior beyond that: the message is removed from its current folder, labels survive the move, and label targets are actively refused. It also warns that folder creation is out of scope, which prevents a predictable failure mode.

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?

Front-loaded with the action, then the semantics, then the exclusion, then the precondition — a logical order with no filler sentences. It runs slightly long at five sentences, and the label-refusal point is stated twice in close succession.

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 3-parameter mutation tool with no output schema and full schema coverage, the description covers the semantics, the valid target domain, the sibling alternative, and the precondition. An agent has everything needed to call it correctly or route elsewhere.

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 the baseline is 3; the description goes beyond it by establishing that only folder paths are legal for 'target' and that labels will be rejected, which the schema does not say. The 'mailbox' shortcut's cost is covered in the schema rather than the description, so the added value is real but partial.

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 ('Moves') plus resource ('messages') plus destination ('into a folder'), and the second sentence explains the Proton-specific semantics that a message lives in exactly one folder. It also explicitly distinguishes itself from add_label, so an agent can route between move_messages, add_label, and trash_messages without opening a schema.

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?

Gives explicit when-to-use (folders as destinations), when-not (labels are refused here, use add_label instead), and prerequisites (the destination must already exist; the server does not create folders). The alternative tool is named rather than implied.

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

Deploy Server

Other Tools