Skip to main content
Glama
googlarz

Proton Mail Bridge MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

apply_thread_action

Destructive

Apply a mailbox action to every message in a conversation thread. Use threadId to archive, mark read, star, or move all messages; dryRun previews impact and unreadOnly limits scope.

Instructions

Apply a reversible mailbox action to every message in a normalized thread at once. Use when you want to act on a full thread identified by threadId (e.g. archive or mark-read an entire conversation). Supports dryRun, unreadOnly to scope impact, and syncBefore to refresh the index first. Prefer batch_email_action when you have explicit emailIds rather than a threadId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
dryRunNoPreview the impact without mutating the mailbox.
threadIdYesThread id from get_threads or get_actionable_threads.
syncBeforeNoRefresh the local mailbox index from IMAP before resolving the thread.
unreadOnlyNoOnly apply the action to unread messages in the thread.
maxBatchSizeNoMaximum number of messages to process. Defaults to 500. Use to prevent runaway operations.
targetFolderNoRequired when action is move.
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. Addedv1.17.0
  3. Removedv1.13.11
  4. 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: +"Required when action is move."
  5. First observedv0.1.0

TDQS

A3.7/5.0
Behavior1/5

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

The description calls the action 'reversible', but the annotation destructiveHint=true and the action enum includes 'delete', which is a direct contradiction. The dryRun and syncBefore disclosures are useful, but the misleading reversibility claim is a serious transparency problem.

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?

Three focused sentences with no filler. The core action is front-loaded, usage context follows, and the alternative tool is named at the end. Every sentence earns its place.

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

Completeness3/5

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

The description provides strong selection guidance and parameter hints, but for a destructive-capable tool with no output schema, it should not claim reversibility and should at least acknowledge the destructive delete option. The contradiction with the annotation leaves an important gap.

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

Parameters3/5

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

Schema description coverage is 88%, so the schema already documents most parameters. The description adds contextual framing for dryRun, unreadOnly, and syncBefore, but it does not clarify targetFolder requirements or maxBatchSize beyond what the schema provides. Baseline 3 is appropriate.

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?

States a specific verb and resource: 'Apply a reversible mailbox action to every message in a normalized thread at once.' It clearly identifies the target as a thread identified by threadId, gives concrete examples like archive or mark-read, and distinguishes itself from batch_email_action and other 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?

Explicitly says when to use this tool: when acting on a full thread identified by threadId. It also gives a clear exclusion: prefer batch_email_action when explicit emailIds are available. Additional scoping options like dryRun, unreadOnly, and syncBefore are mentioned.

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