Skip to main content
Glama
sweetrb

apple-mail-mcp

by sweetrb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

forward-message

Forward an existing email to new recipients with an optional note, or save it as a draft instead of sending immediately.

Instructions

Use when: forwarding an existing message (by id) to new recipients (to is an array), with an optional body to prepend. Set send=false to save as a draft. Returns: a confirmation that the message was forwarded or saved as a draft; over SMTP, also whether a Sent-folder copy was filed (sentCopy). Do not use when: replying to the sender/recipients (use reply-to-message) or composing a new message (use send-email / create-draft). Safety: with the default send=true this SENDS real email immediately and cannot be unsent — require explicit user confirmation of the recipients and any prepended body, or pass send=false to let the user review.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
toYes
bodyNoOptional message to prepend (plain text)
sendNoSend immediately (false = save as draft)
transportNoSMTP sends clean MIME and preserves reply threading; requires SMTP configuration. AppleScript uses Mail.app and may quote-wrap the new body on macOS 15+. Omit to prefer configured SMTP when sending; drafts use AppleScript. A selected SMTP transport never silently falls back. SMTP with send=false is rejected.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
okNo
sentNo
sentCopyNoSMTP only: whether a best-effort copy was filed to the account's Sent mailbox over IMAP (issue #220). Absent when no configured IMAP account matches the SMTP identity — not a failure, the feature simply wasn't engaged.
messageIdNo
transportNo
recipientsNo
sentCopyErrorNoPresent only when sentCopy is false: why the Sent-folder copy failed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.19.12
    • changedInput schema / properties / body / description
      Previous value: -"Optional message to prepend"New value: +"Optional message to prepend (plain text)"
  2. Changed2 schema fields changedv2.18.0
    • addedOutput schema / properties / sentCopy
      Added value: +{
+  "description": "SMTP only: whether a best-effort copy was filed to the account's Sent mailbox over IMAP (issue #220). Absent when no configured IMAP account matches the SMTP identity — not a failure, the feature simply wasn't engaged.",
+  "type": "boolean"
+}
    • addedOutput schema / properties / sentCopyError
      Added value: +{
+  "description": "Present only when sentCopy is false: why the Sent-folder copy failed.",
+  "type": "string"
+}
  3. Changed3 schema fields changedv2.17.8
    • addedInput schema / properties / transport
      Added value: +{
+  "description": "SMTP sends clean MIME and preserves reply threading; requires SMTP configuration. AppleScript uses Mail.app and may quote-wrap the new body on macOS 15+. Omit to prefer configured SMTP when sending; drafts use AppleScript. A selected SMTP transport never silently falls back. SMTP with send=false is rejected.",
+  "enum": [
+    "applescript",
+    "smtp"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / messageId
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / transport
      Added value: +{
+  "enum": [
+    "smtp",
+    "applescript"
+  ],
+  "type": "string"
+}
  4. Changed2 schema fields changedv2.10.24
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  5. Changed1 schema field changedv2.10.8
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
  6. Addedv2.9.0
  7. Removedv2.8.10
  8. First observedv2.6.1

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It clearly warns that send=true sends real email immediately, cannot be unsent, and requires explicit user confirmation, and explains send=false as a reviewable draft path.

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 structured into scannable labeled sections: Use when, Returns, Do not use when, and Safety. Every sentence adds operational value, with the most critical safety warning placed last but clearly emphasized.

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?

For a high-risk send action with no annotations, this description is complete: it covers when to use, when not to use, return behavior, draft mode, SMTP sentCopy, and safety requirements. The output schema further covers return details, so nothing essential is missing.

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 only 60%, but the description explicitly clarifies the undocumented id and to parameters: existing message by id and recipients as an array. It also adds semantic meaning to body ('prepend') and send ('save as draft'), going beyond the raw schema.

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?

States a specific verb and resource: forwards an existing message by id to new recipients (to is an array), with optional prepended body and a draft mode. It clearly distinguishes itself from reply-to-message, send-email, and create-draft, so an agent can tell them apart.

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 'Use when' and 'Do not use when' guidance, naming the exact sibling tools to use instead (reply-to-message, send-email, create-draft). This leaves no ambiguity about when to select this tool.

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