Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_mark

Mark an email as read or unread, starred, or flagged across Gmail, Outlook, iCloud, and IMAP accounts to keep inbox status accurate without opening each message.

Instructions

Mark an email as read/unread, starred, or flagged

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>",
      "emailId": "<emailId>"
    },
    "name": "email_mark"
  }
}

Input Schema

NameRequiredDescriptionDefault
readNo
emailIdYes
flaggedNo
starredNo
accountIdYes
sourceFolderNoSource folder (required for IMAP/iCloud when email is not in INBOX)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It names the toggled states but does not say whether the operation is idempotent, whether setting read=false explicitly marks unread, whether multiple flags can be combined in one call, or what permissions/account context are required.

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?

A single front-loaded sentence with no filler. It is efficient, though arguably too terse given six parameters and mutation semantics.

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 six-parameter mutation tool with no annotations, no output schema, and low schema coverage, the description is materially incomplete. It omits account targeting, folder context, flag-combination behavior, and any indication of what happens on success or failure.

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

Parameters2/5

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

Schema description coverage is only 17%, so the description should compensate, but it only implicitly maps 'read/unread', 'starred', and 'flagged' to three booleans. It says nothing about accountId, emailId, or the interaction with sourceFolder for IMAP/iCloud, and does not clarify omitted-vs-false semantics.

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 ('Mark') and resource ('an email') plus the three state dimensions it can toggle: read/unread, starred, flagged. An agent can tell this is a single-email state mutation, though it does not name the sibling email_batch_mark as the bulk alternative.

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 guidance on when to use this versus email_batch_mark, email_label, or email_move. The implied use case is obvious from the verb, but there are no exclusions, prerequisites, or alternative routing cues.

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