Skip to main content
Glama
Sign In
proton-bridge-mcp

proton-bridge-mcp

by Considus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Move to folder

move_to_folder
Idempotent

Move one or many Proton Mail messages to another folder; preview bulk moves with dry_run and confirm them to avoid errors.

Instructions

File one message (uid) or many (uids): move it into another folder (e.g. 'Folders/', 'Archive', 'Trash'). Many at once is GATED: preview with dry_run=true, show the user, then call with confirmed=true.

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": {
      "to_folder": "<to_folder>"
    },
    "name": "move_to_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidNoOne message. Pass this or uids.
uidsNoSeveral messages, as explicit uids. No wildcards.
folderNoSource folder, default INBOX.
dry_runNoPreview exactly what would happen and change nothing. Needs no confirmation.
confirmedNoRequired whenever uids is used.
to_folderYes
uidvalidityNoUIDVALIDITY reported alongside the uid. Pass it back so a mailbox resync cannot make this act on the wrong message.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • addedInput schema / properties / confirmed
      Added value: +{
+  "description": "Required whenever uids is used.",
+  "type": "boolean"
+}
    • addedInput schema / properties / uid / description
      Added value: +"One message. Pass this or uids."
    • addedInput schema / properties / uids
      Added value: +{
+  "description": "Several messages, as explicit uids. No wildcards.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "uid",
-  "to_folder"
-]New value: +[
+  "to_folder"
+]
  2. First observedv1.2.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnly=false, destructive=false, idempotent=true, and openWorld=true. The description adds the critical bulk gating behavior beyond the annotations, though it does not mention permissions, error behavior, or explicitly confirm that the message is removed from the source folder.

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 tight sentences, front-loaded with the action and immediately followed by the bulk-move gate. No filler; every clause conveys operational information.

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?

For a seven-parameter mutation tool with no output schema, the description covers the core action, folder examples, and the high-risk bulk workflow, while annotations cover safety. It is complete enough to invoke correctly, though it omits explicit mention of the required to_folder parameter and the uidvalidity safeguard already documented in the schema.

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?

With 86% schema coverage the baseline is 3, and the description adds real meaning by explaining the uid/uids choice and tying uids to the dry_run/confirmed gate. It also gives to_folder path examples, while leaving uidvalidity and the source folder parameter to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('File... move it into another folder') and covers both single-message and bulk operations with concrete folder examples. It does not explicitly contrast with sibling label or mark tools, so sibling differentiation is left implicit.

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?

It gives clear operational context for bulk moves: preview with dry_run=true, show the user, then call with confirmed=true. It does not state when to use this tool versus apply_label, mark, or other message-management siblings.

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