Skip to main content
Glama

Mail Mark Message

mail_mark_message

Mark an Apple Mail message as read or unread by message ID, so you can track which emails still need attention.

Instructions

Mark read/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_id": "<message_id>"
    },
    "name": "mail_mark_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
is_readNo
message_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, and it discloses almost nothing: not whether the change is reversible, whether it affects threads or folders, or what permissions are needed. The most consequential behavior, that is_read defaults to true so calling with only message_id silently marks the message read, is left entirely to the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single compact phrase with zero wasted words and the action is front-loaded, but the brevity comes at the cost of specification rather than from efficient packaging of real content.

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?

An output schema exists, so return values need not be described. However, for a state-mutating mail tool with no annotations and zero parameter documentation, the definition omits the default-driven behavior and scope that an agent needs before calling it safely.

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 0%, so the description must compensate for both parameters. It hints at the read/unread polarity of is_read but never explains the default of true or that message_id is the required identifier, leaving the mutation semantics ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "Mark read/unread" gives a verb plus the state being changed, and the tool name supplies the resource (a mail message). It is not tautological, but it never states explicitly that the target is a single message nor how this differs from siblings like mail_move_message or mail_search.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as moving or searching messages. The agent must infer the use case entirely from the two-word description.

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