Skip to main content
Glama
Sign In
Apple Mail

Apple Mail

by yu2001-s
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

mark-as-unread

Marks a specific email message as unread using its message ID. Obtain the ID from search or list operations.

Instructions

Use when: marking a single message (by id) as unread. Returns: a confirmation that the message was marked unread. Do not use when: marking several at once (use batch-mark-as-unread) or marking read (use mark-as-read). Get the id from search-messages or list-messages first.

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": {
      "id": "<id>"
    },
    "name": "mark-as-unread"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
idNo
okNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description must bear full transparency burden. It discloses the return ('a confirmation that the message was marked unread'), which is adequate for a simple state toggle. However, it does not mention idempotency or permissions, though these are implied by the tool's simplicity.

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 extremely concise with three sentences—no superfluous words. It fronts the usage guidance and return value, making it easy to scan.

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?

For a single-parameter tool with an output schema, the description covers purpose, usage context, prerequisites (getting the id), and return value. It lacks only minor details like whether marking an already unread message is a no-op, but overall it is sufficiently complete.

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 description coverage is 0%, so the description must compensate. It explains that the id parameter identifies the message and where to obtain it ('Get the id from search-messages or list-messages first'), but does not clarify the pattern or accepted formats, leaving some ambiguity.

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 explicitly states 'marking a single message (by id) as unread,' clearly defining the verb and resource. It distinguishes from sibling tools like 'batch-mark-as-unread' and 'mark-as-read' by specifying single vs. batch and unread vs. read.

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?

Provides explicit when-to-use ('marking a single message as unread') and when-not-to-use ('Do not use when: marking several at once... or marking read'), with direct references to alternative tools (batch-mark-as-unread, mark-as-read). Also instructs to obtain id from search-messages or list-messages.

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