apple-mail-mcp

Overview Schema Source Related Servers Discussions Admin

Schedule an email

schedule_email

Freeze an email now and schedule its delivery at a set time, either locally or through Exchange. Specify recipients, subject, body, and send time to queue messages in advance.

Instructions

Freeze an email now and schedule local or Exchange-side delivery.

Input Schema

TableJSON Schema

Name	Required	Description
`cc`	No	Optional comma-separated Cc recipients.
`to`	Yes	Comma-separated primary recipients, including optional display names.
`bcc`	No	Optional comma-separated Bcc recipients.
`body`	Yes	Plain-text email content; paragraph breaks are preserved.
`send_at`	Yes	Delivery time in ISO-8601; a timestamp without an offset is local time.
`subject`	Yes	Email subject line.
`attachments`	No	Optional list of local file paths, one path per item.
`from_identity`	No	Configured sending identity; omit it to use the default.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.6.0Sep 13, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {
-      "attachments": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "attempts": {
-        "type": "integer"
-      },
-      "bcc": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "cc": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "created_at": {
-        "type": "string"
-      },
-      "delivered_at": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "executor": {
-        "type": "string"
-      },
-      "graph_draft_id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "id": {
-        "type": "string"
-      },
-      "identity": {
-        "type": "string"
-      },
-      "last_error": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "message_id": {
-        "type": "string"
-      },
-      "next_attempt_at": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "ok": {
-        "const": true
-      },
-      "send_at": {
-        "type": "string"
-      },
-      "status": {
-        "type": "string"
-      },
-      "subject": {
-        "type": "string"
-      },
-      "to": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "ok",
-      "id",
-      "send_at",
-      "created_at",
-      "to",
-      "cc",
-      "bcc",
-      "subject",
-      "attachments",
-      "message_id",
-      "status",
-      "attempts",
-      "next_attempt_at",
-      "last_error",
-      "delivered_at",
-      "identity",
-      "executor",
-      "graph_draft_id"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": true,
-    "properties": {
-      "code": {
-        "type": "string"
-      },
-      "error": {
-        "type": "string"
-      },
-      "fix": {
-        "type": "string"
-      },
-      "ok": {
-        "const": false
-      },
-      "operation_id": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "ok",
-      "code",
-      "error"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "accepted": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "attachments": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "attempts": {
+        "type": "integer"
+      },
+      "bcc": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "cc": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "claimed_at": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "code": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "created_at": {
+        "type": "string"
+      },
+      "delivered_at": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "executor": {
+        "type": "string"
+      },
+      "graph_draft_id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "id": {
+        "type": "string"
+      },
+      "identity": {
+        "type": "string"
+      },
+      "last_error": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "message_id": {
+        "type": "string"
+      },
+      "next_attempt_at": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "ok": {
+        "const": true
+      },
+      "refused": {
+        "additionalProperties": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "send_at": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      },
+      "subject": {
+        "type": "string"
+      },
+      "to": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "ok",
+      "id",
+      "send_at",
+      "created_at",
+      "to",
+      "cc",
+      "bcc",
+      "subject",
+      "attachments",
+      "message_id",
+      "status",
+      "attempts",
+      "next_attempt_at",
+      "last_error",
+      "delivered_at",
+      "identity",
+      "executor",
+      "graph_draft_id",
+      "accepted",
+      "refused",
+      "code",
+      "claimed_at"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {
+      "code": {
+        "type": "string"
+      },
+      "error": {
+        "type": "string"
+      },
+      "fix": {
+        "type": "string"
+      },
+      "ok": {
+        "const": false
+      },
+      "operation_id": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "ok",
+      "code",
+      "error"
+    ],
+    "type": "object"
+  }
+]

First observedv0.1.0Aug 26, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly=false, idempotent=false, destructive=false and openWorld=true. The description adds a real behavioral nuance – the message content is captured now while delivery is deferred, and delivery may be local or Exchange-side. It omits cancellability, auth requirements, and whether a scheduled item surfaces in list_scheduled.

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

Conciseness4/5

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

A single tight sentence that leads with the verb and the key behavioral idea ('freeze... now'). Nothing is wasted, though 'freeze' is slightly jargon-y and could be clarified.

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

Completeness3/5

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

An output schema and annotations exist and the schema fully documents parameters, so the description needn't explain return values. However, for a scheduling mutation the agent would benefit from knowing the result is a cancellable scheduled item and how it relates to list_scheduled/cancel_scheduled, which is absent.

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 every one of the 8 parameters is fully documented in the schema. The description contributes no additional parameter meaning (e.g., no notes on send_at timezone handling or attachment paths), so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb (schedule) and resource (email) plus the distinctive mechanism ('freeze an email now' with deferred delivery). This implicitly separates it from send_email and create_draft, though it never names the siblings. Clear but no explicit sibling differentiation.

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?

Usage is only implied: 'freeze now, schedule delivery' suggests this is the choice when you want deferred rather than immediate sending. There is no explicit statement of when to use this over send_email or cancel_scheduled, and no prerequisites are given.

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