Skip to main content
Glama
sethbang

proton-mail-mcp

flag_thread

Idempotent

Apply flag changes to every message in a conversation thread by specifying one message's ID. Resolves the full reply chain, optionally across folders.

Instructions

Add or remove flags on every message in a thread, identified by Message-ID. Use this instead of update_message_flags when you want the change applied to a whole conversation, or bulk_update_flags when you have a flat set of UIDs rather than a thread. At least one of flagsToAdd/flagsToRemove must be non-empty. acrossFolders:false by default. dryRun:true previews.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageIdYesRFC 5322 Message-ID of any message in the thread (e.g. `<abc@example.com>`); the whole reply chain is resolved from it.
flagsToAddNoFlags to add to every message in the thread. System flags include the backslash (e.g. ["\\Seen", "\\Flagged"]); user keywords are bare alphanumerics (e.g. ["Important"]). At least one of flagsToAdd/flagsToRemove must be non-empty.
flagsToRemoveNoFlags to remove from every message in the thread (e.g. ["\\Seen"] to mark the whole thread unread, or ["\\Flagged"] to unstar).
acrossFoldersNoWhen false (default), act only within the seed message's folder. When true, walk INBOX + Sent + All Mail so the flag change covers thread members in other folders.
dryRunNoWhen true, preview which messages would be updated (per folder) without changing any flags.
Behavior4/5

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

Annotations already provide readOnlyHint=false and idempotentHint=true. Description adds useful behavioral details: default values for acrossFolders and dryRun, and preview behavior. No contradictions.

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 sentences, no wasted words. Front-loaded with purpose, then usage guidance, then defaults/constraints.

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?

Covers when to use, precondition, and behavioral defaults. However, missing return value information (e.g., what the tool outputs), which is relevant since no output schema is provided.

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 covers all parameters with descriptions (100% coverage), so baseline is 3. Description adds some extra context like the non-empty constraint and default values but does not significantly augment beyond schema.

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?

Description clearly states the tool operates on a thread by Message-ID, distinguishing it from sibling tools like update_message_flags (single message) and bulk_update_flags (flat UIDs).

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 tells when to use and when to use alternatives, and states the precondition that at least one of flagsToAdd/flagsToRemove must be non-empty.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sethbang/proton-mail-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server