Skip to main content
Glama
yu2001-s

Apple Mail

by yu2001-s
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

resolve-message-id

Resolves IMAP message IDs to numeric Mail.app IDs, enabling color flagging that only works with numeric IDs. Use when you need to apply a colored flag to an IMAP-flagged message.

Instructions

Use when: you have imap: message id(s) and need the numeric Mail.app id(s) — most importantly to apply a flag COLOR, which only sticks on the AppleScript numeric-id path (IMAP \Flagged is colorless, so a smart mailbox keyed on flag color never matches an IMAP-flagged message). Each imap: id is resolved via its RFC822 Message-ID. Returns: for each input id, its numericId (the AppleScript id) or null when it can't be resolved, plus the messageId used; and a resolvedCount. Do not use when: your ids are already numeric (they pass straight through), or you don't need a color — flag/move/mark tools operate on imap: ids directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
resolvedNo
resolvedCountNo

Tool Definition Quality

A5/5.0
Behavior5/5

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

No annotations provided, but description fully discloses the behavioral context: why numeric IDs are needed for color flags, resolution via RFC822 Message-ID, and return format including null for unresolvable IDs.

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?

Concise 4-sentence description with front-loaded key use case, no unnecessary words, and clear separation between usage guidance and output specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, description covers input format, output structure, motivation, and alternative tools—complete for a single-parameter resolution tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description adds meaning by explaining the imap: prefix, the resolution process, and the pass-through for numeric IDs, compensating fully for lack of param documentation.

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 clearly states it resolves imap: message IDs to numeric Mail.app IDs, specifically for applying flag colors. It distinguishes from sibling tools like flag-message by explaining the color limitation.

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?

Explicitly provides 'Use when' and 'Do not use when' conditions, including when to use alternative tools (flag/move/mark for non-color operations).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yu2001-s/apple-mail'

If you have feedback or need assistance with the MCP directory API, please join our Discord server