Skip to main content
Glama
googlarz

Proton Mail Bridge MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

batch_email_action

Destructive

Apply one action to a known list of email IDs in a single pass: archive, trash, move, mark read/unread, star, restore, or delete. Supports dryRun to preview before applying.

Instructions

Apply one action to a known list of email IDs in a single IMAP pass. Use when you already have the IDs and want to archive, trash, move, mark-read/unread, star/unstar, restore, or permanently delete them. Actions: mark_read, mark_unread, star, unstar, archive, trash, restore, move (requires targetFolder), delete (permanent expunge). Supports dryRun. Prefer bulk_delete when selecting messages by search criteria (from/subject/date) rather than by ID. Prefer apply_thread_action when acting on a thread by threadId. Prefer empty_folder to clear an entire folder.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
dryRunNoPreview the impact without mutating the mailbox.
emailIdsYesComposite email ids as an array or a comma-separated string.
maxBatchSizeNoMaximum number of messages to process. Defaults to 500. Use to prevent runaway operations.
targetFolderNoDestination folder. Required when action is 'move'; optional for 'restore' (defaults to INBOX).
continueOnErrorNoContinue applying the action after an individual failure.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.8
    • addedInput schema / properties / maxBatchSize
      Added value: +{
+  "description": "Maximum number of messages to process. Defaults to 500. Use to prevent runaway operations.",
+  "type": "number"
+}
  2. Changed2 schema fields changedv1.13.4
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "mark_read",
-  "mark_unread",
-  "star",
-  "unstar",
-  "archive",
-  "trash",
-  "restore"
-]New value: +[
+  "mark_read",
+  "mark_unread",
+  "star",
+  "unstar",
+  "archive",
+  "trash",
+  "restore",
+  "move",
+  "delete"
+]
    • changedInput schema / properties / targetFolder / description
      Previous value: -"Optional restore destination. Used only when action is restore."New value: +"Destination folder. Required when action is 'move'; optional for 'restore' (defaults to INBOX)."
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

The annotation only indicates destructiveHint=true, so the description adds meaningful behavioral context: it performs the action in a single IMAP pass, supports dryRun for previewing impact, and clarifies that delete means permanent expunge. This substantially enriches the safety profile beyond the bare destructive hint.

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?

The description is dense but every sentence earns its place: the core behavior, supported actions, key parameter constraint, dryRun support, and routing to alternatives are all covered without filler. The most important usage condition is front-loaded.

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 destructive batch tool with multiple alternatives, the description covers when to use it, what actions are available, and which sibling tools to prefer in other scenarios. It does not describe return values or per-message error reporting, but those are not critical for tool selection and some are already covered by schema fields like continueOnError.

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 high (83%), but the description adds useful semantic context by grouping actions, noting that move requires targetFolder, highlighting dryRun, and clarifying deletion is permanent. This goes beyond the raw schema and helps an agent choose valid parameter combinations.

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 states a clear verb and resource: applying one action to a known list of email IDs in a single IMAP pass. It enumerates the exact supported actions and explicitly distinguishes this tool from bulk_delete, apply_thread_action, and empty_folder, so an agent can tell it apart from relevant siblings.

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?

The description gives direct when-to-use guidance: use it when you already have the email IDs. It also names concrete alternatives with the conditions that select them, such as preferring bulk_delete for search-criteria-based selection, apply_thread_action for thread IDs, and empty_folder for clearing a whole folder.

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