Skip to main content
Glama
sweetrb

apple-mail-mcp

by sweetrb

forward-message

Forward an existing email by ID to new recipients, optionally prepend text and add attachments, or save it as a draft for review.

Instructions

Use when: forwarding an existing message (by id) to new recipients (to is an array), with an optional body to prepend and optional extra attachments (same rules as send-email). Set send=false to save as a draft. Returns: a confirmation that the message was forwarded or saved as a draft, with the attachment count; 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

NameRequiredDescriptionDefault
idYes
toYes
bodyNoOptional message to prepend (plain text)
sendNoSend immediately (false = save as draft)
accountNoFor a numeric id, the account it was listed from; pair with mailbox. Omit for an imap: id.
mailboxNoFor a numeric id, the exact source mailbox path; pair with account. A miss never searches elsewhere.
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.
attachmentsNoFiles to attach: absolute paths in the configured attachment read roots (e.g. '/Users/me/Documents/report.pdf') and/or inline {filename, contentBase64} objects up to 25 MiB decoded each.
compositionNoOpt in to Mail's visible native editor: inserts only new prose, preserving its signature, HTML quotation and reply ancestry without the AppleScript content setter. Requires an unlocked desktop and existing Accessibility and Automation permissions. Uses Mail.app even when SMTP is configured; cannot be combined with transport=smtp or caller-built threading headers. New messages require an explicit account. Do not interact with Mail or the clipboard while it runs. Failure never falls back to another composition method or sends an unverified message.

Output Schema

NameRequiredDescriptionDefault
idNo
okNo
sentNo
partialNoSMTP accepted some recipients and rejected others; do not resend to accepted recipients.
acceptedNoRecipients accepted by the SMTP server, not final inbox delivery.
rejectedNoRecipients rejected by the SMTP server.
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.
attachmentCountNo
deliveryUnknownNoSMTP returned no definitive submission result. Verify before retrying.
sentCopyAlreadyFiledNoPresent (true) only when sentCopy is true because the Sent mailbox already held this Message-ID (e.g. Gmail's SMTP files its own copy), so none was appended.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.20.52
    • addedOutput schema / properties / accepted
      Added value: +{
      +  "description": "Recipients accepted by the SMTP server, not final inbox delivery.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / deliveryUnknown
      Added value: +{
      +  "description": "SMTP returned no definitive submission result. Verify before retrying.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / partial
      Added value: +{
      +  "description": "SMTP accepted some recipients and rejected others; do not resend to accepted recipients.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / rejected
      Added value: +{
      +  "description": "Recipients rejected by the SMTP server.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Changed2 schema fields changedv2.20.45
    • addedInput schema / properties / account
      Added value: +{
      +  "description": "For a numeric id, the account it was listed from; pair with mailbox. Omit for an imap: id.",
      +  "type": "string"
      +}
    • addedInput schema / properties / mailbox
      Added value: +{
      +  "description": "For a numeric id, the exact source mailbox path; pair with account. A miss never searches elsewhere.",
      +  "type": "string"
      +}
  3. Changed1 schema field changedv2.20.39
    • addedInput schema / properties / composition
      Added value: +{
      +  "const": "native-editor",
      +  "description": "Opt in to Mail's visible native editor: inserts only new prose, preserving its signature, HTML quotation and reply ancestry without the AppleScript content setter. Requires an unlocked desktop and existing Accessibility and Automation permissions. Uses Mail.app even when SMTP is configured; cannot be combined with transport=smtp or caller-built threading headers. New messages require an explicit account. Do not interact with Mail or the clipboard while it runs. Failure never falls back to another composition method or sends an unverified message.",
      +  "type": "string"
      +}
  4. Changed1 schema field changedv2.20.29
    • addedOutput schema / properties / sentCopyAlreadyFiled
      Added value: +{
      +  "description": "Present (true) only when sentCopy is true because the Sent mailbox already held this Message-ID (e.g. Gmail's SMTP files its own copy), so none was appended.",
      +  "type": "boolean"
      +}
  5. Changed2 schema fields changedv2.20.11
    • addedInput schema / properties / attachments
      Added value: +{
      +  "description": "Files to attach: absolute paths in the configured attachment read roots (e.g. '/Users/me/Documents/report.pdf') and/or inline {filename, contentBase64} objects up to 25 MiB decoded each.",
      +  "items": {
      +    "anyOf": [
      +      {
      +        "description": "Absolute path to an existing file in an allowed read root",
      +        "type": "string"
      +      },
      +      {
      +        "additionalProperties": false,
      +        "properties": {
      +          "contentBase64": {
      +            "description": "Base64-encoded file content (maximum 25 MiB decoded)",
      +            "maxLength": 69905072,
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "filename": {
      +            "description": "Filename to give the attachment",
      +            "maxLength": 255,
      +            "minLength": 1,
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "filename",
      +          "contentBase64"
      +        ],
      +        "type": "object"
      +      }
      +    ]
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
    • addedOutput schema / properties / attachmentCount
      Added value: +{
      +  "type": "number"
      +}
  6. 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)"
  7. 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"
      +}
  8. 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"
      +}
  9. 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"
  10. Changed1 schema field changedv2.10.8
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
  11. Addedv2.9.0
  12. Removedv2.8.10
  13. First observedv2.6.1

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations supplied, the description fully addresses the central risk: the default send=true immediately sends real, irreversible email. It requires explicit confirmation of recipients and prepended content, offers draft mode for review, and discloses the SMTP-specific sentCopy result.

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 labeled Use when, Returns, Do not use when, and Safety sections make the definition easy to scan, with the operation and safety-critical default front-loaded appropriately. Its length is justified by the tool's irreversible behavior and draft alternative, with no substantial filler.

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?

Together with the detailed input schema and existing output schema, the description provides everything needed to select and safely invoke the tool. Complex transport and composition constraints remain available in the schema, while the description covers the essential workflow, alternatives, results, and confirmation requirement.

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

Parameters4/5

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

The description usefully documents the two schema-undocumented parameters by explaining that id identifies the source message and to is an array of new recipients. It reinforces body, attachments, and send semantics, but leaves most transport, account/mailbox, and composition details to the already-rich schema rather than adding further context.

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 precisely states that the tool forwards an existing message identified by id to new recipients, with optional prepended text, extra attachments, or draft saving. It also clearly distinguishes forwarding from replying and composing a new message.

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?

Explicit “Use when” and “Do not use when” guidance covers the primary use case and exclusions. It names reply-to-message for replies and send-email or create-draft for new composition, while also explaining when send=false is appropriate.

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