apple-mail-mcp

Overview Schema Source Related Servers Discussions Admin

flag_email

Set or clear a flag on an email message. Provide the message reference and a boolean to indicate whether to flag or unflag.

Instructions

Set or clear the flag on an email.

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>",
      "flagged": "<flagged>"
    },
    "name": "flag_email"
  }
}

Input Schema

Name	Required	Description	Default
`flagged`	Yes	True to flag the message, false to unflag it.
`message_ref`	Yes	Composite message reference from list_emails or search_emails.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 4, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It clearly names the action but does not disclose any side effects, permissions, or return behavior. For a simple mutation, this is adequate but not enhanced.

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 concise sentence with no filler. It fully conveys the tool's purpose in seven words.

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?

The tool is simple, has only two parameters with full schema descriptions, and no output schema is expected. The description covers the core action, though it could mention that the flag is toggled on the specified message. Overall, it is complete for practical use.

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 the parameters are fully documented in the schema. The description adds no additional parameter semantics, so the baseline score of 3 applies.

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 'Set or clear the flag on an email' clearly states the action (set/clear) and the resource (email flag), distinguishing it from sibling tools like mark_read or archive_email. The verb is specific and unambiguous.

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?

The description implies the tool is used to flag or unflag an email but provides no explicit guidance on when to use it versus alternatives. No exclusions or conditions are mentioned.

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