outlook-mcp

outlook_create_draft

Creates a reviewable Outlook email draft before sending, including optional replies, forwards, and scheduled delivery.

Instructions

Create a draft email for later review/send (pair with outlook_send_draft).

Use this when a human should review before sending; use outlook_send_message to send immediately without review. reply_to_message_id (reply_all=True for all) or forward_message_id drafts in that thread, quoting the original; on a reply, Graph fills to/cc/subject, so pass [] for a recipient you want cleared and omit the argument to keep Graph's choice. Pass deferred_send_datetime (ISO 8601, e.g. "2026-05-06T08:00:00Z") to schedule delayed delivery — Exchange holds the message server-side after outlook_send_draft. Pass reply_to to pre-populate the Reply-To header.

Input Schema

Name	Required	Default
`cc`	No
`to`	No
`bcc`	No
`body`	Yes
`is_html`	No
`subject`	No
`reply_to`	No
`reply_all`	No
`importance`	No	normal
`is_markdown`	No
`forward_message_id`	No
`reply_to_message_id`	No
`deferred_send_datetime`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed42 schema fields changedv1.30.2Oct 30, 2026
- removedInput schema / properties / bcc / anyOf
```
Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / bcc / default
```
Removed value: -null
```
- addedInput schema / properties / bcc / items
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / bcc / title
```
Removed value: -"Bcc"
```
- addedInput schema / properties / bcc / type
```
Added value: +"array"
```
- removedInput schema / properties / body / title
```
Removed value: -"Body"
```
- removedInput schema / properties / cc / anyOf
```
Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / cc / default
```
Removed value: -null
```
- addedInput schema / properties / cc / items
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / cc / title
```
Removed value: -"Cc"
```
- addedInput schema / properties / cc / type
```
Added value: +"array"
```
- removedInput schema / properties / deferred_send_datetime / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / deferred_send_datetime / default
```
Removed value: -null
```
- removedInput schema / properties / deferred_send_datetime / title
```
Removed value: -"Deferred Send Datetime"
```
- addedInput schema / properties / deferred_send_datetime / type
```
Added value: +"string"
```
- removedInput schema / properties / forward_message_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / forward_message_id / default
```
Removed value: -null
```
- removedInput schema / properties / forward_message_id / title
```
Removed value: -"Forward Message Id"
```
- addedInput schema / properties / forward_message_id / type
```
Added value: +"string"
```
- removedInput schema / properties / importance / title
```
Removed value: -"Importance"
```
- removedInput schema / properties / is_html / title
```
Removed value: -"Is Html"
```
- removedInput schema / properties / is_markdown / title
```
Removed value: -"Is Markdown"
```
- removedInput schema / properties / reply_all / title
```
Removed value: -"Reply All"
```
- removedInput schema / properties / reply_to / anyOf
```
Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / reply_to / default
```
Removed value: -null
```
- addedInput schema / properties / reply_to / items
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / reply_to / title
```
Removed value: -"Reply To"
```
- addedInput schema / properties / reply_to / type
```
Added value: +"array"
```
- removedInput schema / properties / reply_to_message_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / reply_to_message_id / default
```
Removed value: -null
```
- removedInput schema / properties / reply_to_message_id / title
```
Removed value: -"Reply To Message Id"
```
- addedInput schema / properties / reply_to_message_id / type
```
Added value: +"string"
```
- removedInput schema / properties / subject / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / subject / default
```
Removed value: -null
```
- removedInput schema / properties / subject / title
```
Removed value: -"Subject"
```
- addedInput schema / properties / subject / type
```
Added value: +"string"
```
- removedInput schema / properties / to / anyOf
```
Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / to / default
```
Removed value: -null
```
- addedInput schema / properties / to / items
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / to / title
```
Removed value: -"To"
```
- addedInput schema / properties / to / type
```
Added value: +"array"
```
- removedInput schema / title
```
Removed value: -"outlook_create_draftArguments"
```

Changed12 schema fields changedv1.28.0Oct 25, 2026

addedInput schema / properties / forward_message_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Forward Message Id"
+}

addedInput schema / properties / is_markdown

Added value: +{
+  "default": false,
+  "title": "Is Markdown",
+  "type": "boolean"
+}

addedInput schema / properties / reply_all

Added value: +{
+  "default": false,
+  "title": "Reply All",
+  "type": "boolean"
+}

addedInput schema / properties / reply_to_message_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Reply To Message Id"
+}

addedInput schema / properties / subject / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / subject / default
```
Added value: +null
```
removedInput schema / properties / subject / type
```
Removed value: -"string"
```

addedInput schema / properties / to / anyOf

Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / to / default
```
Added value: +null
```
removedInput schema / properties / to / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / to / type
```
Removed value: -"array"
```

changedInput schema / required

Previous value: -[
-  "to",
-  "subject",
-  "body"
-]New value: +[
+  "body"
+]

First observedv1.11.0Jun 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly=false and destructive=false. The description adds meaningful behavior beyond that: drafts are for later review/send, deferred_send_datetime schedules server-side holding after outlook_send_draft, and Graph's reply auto-fill can be overridden by passing [] versus omitting a recipient.

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 dense but front-loaded: it leads with purpose and alternative, then uses compact parentheticals for scheduling and reply/forward semantics. For a 13-parameter tool with no schema descriptions, the length is justified and no sentence is filler.

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?

Given 13 parameters, no output schema, and minimal annotations, the description covers the non-obvious threading, forwarding, and scheduling behavior well. It is less complete on basic formatting flags and some recipient fields, but an agent can still call it correctly for common draft creation.

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?

With 0% schema description coverage across 13 parameters, the description compensates for several non-obvious ones: reply_to_message_id, reply_all, forward_message_id, deferred_send_datetime, and reply_to. It also explains the subtle [] versus omitted behavior for reply recipients. However, it leaves bcc, is_html, is_markdown, importance, and body format semantics undocumented, so coverage remains partial.

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 states a specific verb and resource ('Create a draft email') and explicitly distinguishes the draft workflow from immediate sending by naming outlook_send_message and outlook_send_draft. An agent can identify the tool's role without inspecting siblings.

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?

It gives explicit when-to-use guidance: choose this when a human should review before sending, and use outlook_send_message for immediate send without review. It also says to pair with outlook_send_draft, covering the follow-up action.

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

Deploy Server

outlook_create_draft

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools