Skip to main content
Glama

mark_read

Idempotent

Marks up to 100 messages as read or unread by ID, opening Mail hidden in the background when needed.

Instructions

Mark messages (at most 100) as read or unread. If Mail is not running, applesauce opens it hidden in the background and leaves it open.

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

Input Schema

NameRequiredDescriptionDefault
idsYesMessage ids from search_mail. At most 100.
readYestrue for read, false for unread.
in_accountNoAccount id of the message (the 'account_id' field of search_mail). Only needed with 'in_mailbox'.
in_mailboxNoMailbox path of the message (the 'mailbox' field of search_mail). Only needed when Full Disk Access is missing. Give 'in_account' too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (which already declare non-read-only, idempotent, non-destructive), the description discloses a real side effect: if Mail is not running, applesauce launches it hidden and leaves it running afterwards. That persistent app-state change is exactly the kind of behavior an agent cannot infer from structured fields. It omits what the call returns or whether partially invalid ids are skipped.

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?

Two short sentences with the core operation and the batch cap front-loaded, followed by the environment caveat. Every clause carries information; nothing is padded or repeated from the title.

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 mutation tool with full annotation coverage and complete schema descriptions, the definition covers the operation, the 100-message bound, and the notable Mail-launch side effect. The only gap is the absence of return-value information, which matters slightly because there is no output schema.

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 100%, so all four parameters (ids, read, in_account, in_mailbox) are already fully documented in the schema, including the fallback conditions for the two optional ones. The description adds no extra meaning about formats, limits per call, or partial-failure handling, so the baseline 3 applies.

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 messages ... as read or unread") plus a hard batch ceiling of 100, so an agent immediately knows the operation and its scope. It does not distinguish itself from near neighbors such as flag_message, so it stops short of a 5.

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?

Usage context is only implied: the batch limit and the note about Mail being launched suggest this is a follow-up to a search, but the description never says when to prefer this over flag_message or get_message. No explicit exclusions or alternatives are named.

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