Skip to main content
Glama
Sign In
apple-mail-mcp

apple-mail-mcp

by jayvee6
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

mark_read

Mark an email as read or unread in Apple Mail using its message reference.

Instructions

Mark an email as read or unread.

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": {
      "message_ref": "<message_ref>",
      "read": "<read>"
    },
    "name": "mark_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
readYesTrue to mark as read, false to mark as unread.
message_refYesComposite message reference from list_emails or search_emails.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden but only states the core action. It does not disclose potential side effects (e.g., whether the email must exist) or permissions, though the behavior is straightforward and reversible by setting the boolean.

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?

The description is a single sentence that is front-loaded and contains no wasted words, efficiently conveying the entire purpose.

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?

Given the tool's simplicity (two parameters, no output schema), the description is sufficiently complete. It does not explain return values, but that is not critical for a read/unread toggle. Lacks context about prerequisites, but the action is self-contained.

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 100%, so the parameters are fully documented. The description adds no additional meaning beyond what the schema already provides, keeping it at the baseline.

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?

The description uses a specific verb ('Mark') and resource ('an email') and explicitly states the two possible states ('read or unread'), which clearly distinguishes it from sibling tools like flag_email or archive_email.

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

Usage Guidelines4/5

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

The description implies the usage context: use when you want to change the read status of an email. No exclusions are needed because no sibling tool overlaps with this action, providing clear context without explicit alternatives.

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