Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

mark_email

Marks one or more messages as read or unread and adds or removes stars by UID, with optional folder targeting.

Instructions

Mark one or more messages as (un)read and/or starred.

uids = a single uid OR a list. seen True/False = read/unread, flagged True/False = set/remove star.

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": {
      "uids": "<uids>"
    },
    "name": "mark_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
seenNo
uidsYes
folderNoINBOX
flaggedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a mutation but says nothing about idempotency, error behavior for unknown uids, whether the change is reversible, or what happens if both seen and flagged are left null — significant gaps for an unannotated write tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the purpose and followed by a compact parameter legend. No filler, though the line-broken legend formatting is slightly awkward and could be tightened.

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?

An output schema exists, so return values need no explanation, and the core action is clear. Still, for an unannotated mutation tool the definition omits the folder semantics and the default behavior when neither seen nor flagged is supplied, which an agent needs in order to call it correctly.

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 coverage is 0%, and the description does add real meaning for two params: seen=True/False maps to read/unread and flagged=True/False maps to star/unstar, which the bare schema titles 'Seen'/'Flagged' do not convey. However, the folder parameter (default INBOX) is never explained, and it is unclear whether uids are interpreted within folder, leaving one of four params undocumented.

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?

States a specific verb and resource: 'Mark one or more messages as (un)read and/or starred.' An agent can immediately tell this is a message-state mutation rather than a move, delete, or search, even without an explicit sibling callout.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or when-not-to-use guidance, no mention of alternatives such as move_email or add_label, and no statement of prerequisites (e.g. that uids are scoped to folder). The 'and/or' phrasing implies at least one of seen/flagged should be supplied but never says so.

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