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 list of known email IDs: archive, trash, move, mark read/unread, star/unstar, restore, or permanently delete. Use dryRun to preview changes before mutating the mailbox.

Instructions

Apply one action to a known list of email IDs in a single IMAP pass. 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. 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.

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.7/5.0
Behavior4/5

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

Annotations include destructiveHint=true, and the description reinforces this by noting 'delete (permanent expunge)' and 'move (requires targetFolder).' It also adds the behavioral detail of a 'single IMAP pass' and support for dryRun. It does not contradict the annotations and provides useful extra context, though it could mention the error-handling behavior more explicitly.

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 compact and well-structured: it opens with the core purpose, immediately differentiates from siblings, then lists supported actions and special requirements. Every sentence earns its place; no filler or redundancy.

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 batch action tool with six parameters and a destructive flag, the description covers the essential selection criteria, action semantics, and the dryRun safety feature. It does not describe the return/result format, but since there is no output schema, the agent must infer the response; still, for a mutation tool, the guidance is strong.

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

Parameters5/5

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

Schema coverage is 83% (5/6 params documented), but the description adds significant value by clarifying the action enum meanings (e.g., 'delete' is permanent expunge, 'move' requires targetFolder, restore defaults to INBOX) and highlighting the dryRun flag. This goes beyond the schema's simple 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 a specific verb ('Apply') and resource ('known list of email IDs') and explicitly names sibling tools (bulk_delete, apply_thread_action, empty_folder) it should not be used instead of. It also enumerates the actions it supports, making it unmistakable what the tool does.

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 explicit when-to-use and when-not-to-use guidance, naming three alternatives (bulk_delete for search-based selection, apply_thread_action for threadId, empty_folder for clearing a folder) and the conditions that select each. It also states the prerequisite: 'when you already have the IDs.'

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