Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_batch_mark

Marks multiple emails at once as read or unread, starred, or flagged, letting you update many messages in one batch instead of marking each email individually.

Instructions

Mark multiple emails at once (read/unread, starred, flagged). Much faster than individual marks.

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": {
      "accountId": "<accountId>",
      "emailIds": "<emailIds>"
    },
    "name": "email_batch_mark"
  }
}

Input Schema

NameRequiredDescriptionDefault
readNo
flaggedNo
starredNo
emailIdsYesArray of email IDs to mark
accountIdYes
sourceFolderNoSource folder (required for IMAP/iCloud when emails are not in INBOX)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

B3.1/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 burden. It says nothing about what happens when a flag boolean is omitted (leave unchanged vs. clear), whether flags are set or toggled, permission requirements, partial-failure behavior on large batches, or that up to 1000 IDs are accepted at once.

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 core action and the affected flags; the speed note earns its place as a selection cue. Nothing is redundant.

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

Completeness2/5

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

For a 6-parameter batch mutation with no annotations and no output schema, the definition is thin: it omits flag-omission semantics, batch limits, error behavior, and the sourceFolder caveat, all of which an agent needs to invoke 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 only 33%, and the description adds partial meaning by mapping read/starred/flagged to the markable states. However, it does not explain that these are independent set/unset switches, nor does it mention accountId or sourceFolder, which has a non-obvious IMAP/iCloud requirement documented only in the schema.

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 multiple emails at once') plus the exact flag dimensions affected (read/unread, starred, flagged). It implicitly distinguishes itself from the single-item email_mark sibling, though it never names it.

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

Usage Guidelines3/5

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

The phrase 'Much faster than individual marks' hints that this is the tool to pick for multi-email flag changes, but it never explicitly says when to use it versus email_mark or when to fall back to single marks (e.g., one ID). No prerequisites or exclusions are given.

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