Microsoft 365 MCP Server

create-draft-email

create-draft-email

Destructive

Create a saved Outlook email draft in the user's Drafts folder with subject, body, recipients, and importance, without sending it.

Instructions

Create a draft Outlook email message in the signed-in user's Drafts folder. Set subject, body, toRecipients, ccRecipients, and importance. The draft is saved, not sent — use send-mail to send a message directly, or send the draft afterwards.

Input Schema

Name	Required	Description
`body`	Yes
`confirm`	No	For destructive operations when the confirm gate is enabled (MS365_MCP_REQUIRE_CONFIRM=true; off by default). Set to true only after the user has explicitly approved this action. When the gate is on, calls without confirm: true return { error: "confirmation_required" } without touching user data.
`includeHeaders`	No	Include response headers (including ETag) in the response metadata
`excludeResponse`	No	Exclude the full response body and only return success or failure indication

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.176.1Oct 29, 2026

removedInput schema / properties / body / properties / attachments / items / properties / lastModifiedDateTime / description

Removed value: -"The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z"

removedInput schema / properties / body / properties / createdDateTime / description

Removed value: -"The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z"

removedInput schema / properties / body / properties / lastModifiedDateTime / description

Removed value: -"The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z"

Changed29 schema fields changedv0.145.2Aug 22, 2026

removedInput schema / $defs

Removed value: -{
-  "def0": {
-    "additionalProperties": true,
-    "properties": {
-      "dateTime": {
-        "description": "A single point of time in a combined date and time representation ({date}T{time}; for example, 2017-08-29T04:00:00.0000000).",
-        "type": "string"
-      },
-      "timeZone": {
-        "description": "Represents a time zone, for example, 'Pacific Standard Time'. See below for more possible values.",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  },
-  "def1": {
-    "additionalProperties": true,
-    "properties": {
-      "emailAddress": {
-        "additionalProperties": true,
-        "properties": {
-          "address": {
-            "description": "The email address of the person or entity.",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "name": {
-            "description": "The display name of the person or entity.",
-            "type": [
-              "string",
-              "null"
-            ]
-          }
-        },
-        "type": "object"
-      }
-    },
-    "type": "object"
-  }
-}

removedInput schema / properties / body / properties / bccRecipients / items / $ref
```
Removed value: -"#/$defs/def1"
```
addedInput schema / properties / body / properties / bccRecipients / items / additionalProperties
```
Added value: +true
```

addedInput schema / properties / body / properties / bccRecipients / items / properties

Added value: +{
+  "emailAddress": {
+    "additionalProperties": true,
+    "properties": {
+      "address": {
+        "description": "The email address of the person or entity.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "description": "The display name of the person or entity.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+}

addedInput schema / properties / body / properties / bccRecipients / items / type
```
Added value: +"object"
```
removedInput schema / properties / body / properties / ccRecipients / items / $ref
```
Removed value: -"#/$defs/def1"
```
addedInput schema / properties / body / properties / ccRecipients / items / additionalProperties
```
Added value: +true
```

addedInput schema / properties / body / properties / ccRecipients / items / properties

Added value: +{
+  "emailAddress": {
+    "additionalProperties": true,
+    "properties": {
+      "address": {
+        "description": "The email address of the person or entity.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "description": "The display name of the person or entity.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+}

addedInput schema / properties / body / properties / ccRecipients / items / type
```
Added value: +"object"
```
removedInput schema / properties / body / properties / flag / properties / completedDateTime / $ref
```
Removed value: -"#/$defs/def0"
```
addedInput schema / properties / body / properties / flag / properties / completedDateTime / additionalProperties
```
Added value: +true
```

addedInput schema / properties / body / properties / flag / properties / completedDateTime / properties

Added value: +{
+  "dateTime": {
+    "description": "A single point of time in a combined date and time representation ({date}T{time}; for example, 2017-08-29T04:00:00.0000000).",
+    "type": "string"
+  },
+  "timeZone": {
+    "description": "Represents a time zone, for example, 'Pacific Standard Time'. See below for more possible values.",
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}

addedInput schema / properties / body / properties / flag / properties / completedDateTime / type
```
Added value: +"object"
```
removedInput schema / properties / body / properties / flag / properties / dueDateTime / $ref
```
Removed value: -"#/$defs/def0"
```
addedInput schema / properties / body / properties / flag / properties / dueDateTime / additionalProperties
```
Added value: +true
```

addedInput schema / properties / body / properties / flag / properties / dueDateTime / properties

Added value: +{
+  "dateTime": {
+    "description": "A single point of time in a combined date and time representation ({date}T{time}; for example, 2017-08-29T04:00:00.0000000).",
+    "type": "string"
+  },
+  "timeZone": {
+    "description": "Represents a time zone, for example, 'Pacific Standard Time'. See below for more possible values.",
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}

addedInput schema / properties / body / properties / flag / properties / dueDateTime / type
```
Added value: +"object"
```
removedInput schema / properties / body / properties / flag / properties / startDateTime / $ref
```
Removed value: -"#/$defs/def0"
```
addedInput schema / properties / body / properties / flag / properties / startDateTime / additionalProperties
```
Added value: +true
```

addedInput schema / properties / body / properties / flag / properties / startDateTime / properties

Added value: +{
+  "dateTime": {
+    "description": "A single point of time in a combined date and time representation ({date}T{time}; for example, 2017-08-29T04:00:00.0000000).",
+    "type": "string"
+  },
+  "timeZone": {
+    "description": "Represents a time zone, for example, 'Pacific Standard Time'. See below for more possible values.",
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}

addedInput schema / properties / body / properties / flag / properties / startDateTime / type
```
Added value: +"object"
```
removedInput schema / properties / body / properties / from / $ref
```
Removed value: -"#/$defs/def1"
```
addedInput schema / properties / body / properties / from / additionalProperties
```
Added value: +true
```

addedInput schema / properties / body / properties / from / properties

Added value: +{
+  "emailAddress": {
+    "additionalProperties": true,
+    "properties": {
+      "address": {
+        "description": "The email address of the person or entity.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "description": "The display name of the person or entity.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+}

addedInput schema / properties / body / properties / from / type
```
Added value: +"object"
```
removedInput schema / properties / body / properties / toRecipients / items / $ref
```
Removed value: -"#/$defs/def1"
```
addedInput schema / properties / body / properties / toRecipients / items / additionalProperties
```
Added value: +true
```

addedInput schema / properties / body / properties / toRecipients / items / properties

Added value: +{
+  "emailAddress": {
+    "additionalProperties": true,
+    "properties": {
+      "address": {
+        "description": "The email address of the person or entity.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "description": "The display name of the person or entity.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+}

addedInput schema / properties / body / properties / toRecipients / items / type
```
Added value: +"object"
```

Changed14 schema fields changedv0.134.4Jul 28, 2026

addedInput schema / $defs

Added value: +{
+  "def0": {
+    "additionalProperties": true,
+    "properties": {
+      "dateTime": {
+        "description": "A single point of time in a combined date and time representation ({date}T{time}; for example, 2017-08-29T04:00:00.0000000).",
+        "type": "string"
+      },
+      "timeZone": {
+        "description": "Represents a time zone, for example, 'Pacific Standard Time'. See below for more possible values.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "def1": {
+    "additionalProperties": true,
+    "properties": {
+      "emailAddress": {
+        "additionalProperties": true,
+        "properties": {
+          "address": {
+            "description": "The email address of the person or entity.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "The display name of the person or entity.",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      }
+    },
+    "type": "object"
+  }
+}

changedInput schema / properties / body / properties / bccRecipients / items / $ref
```
Previous value: -"#/properties/body/properties/from"New value: +"#/$defs/def1"
```

changedInput schema / properties / body / properties / ccRecipients / items / $ref

Previous value: -"#/properties/body/properties/from"New value: +"#/$defs/def1"

addedInput schema / properties / body / properties / flag / properties / completedDateTime / $ref
```
Added value: +"#/$defs/def0"
```
removedInput schema / properties / body / properties / flag / properties / completedDateTime / additionalProperties
```
Removed value: -true
```

removedInput schema / properties / body / properties / flag / properties / completedDateTime / properties

Removed value: -{
-  "dateTime": {
-    "description": "A single point of time in a combined date and time representation ({date}T{time}; for example, 2017-08-29T04:00:00.0000000).",
-    "type": "string"
-  },
-  "timeZone": {
-    "description": "Represents a time zone, for example, 'Pacific Standard Time'. See below for more possible values.",
-    "type": [
-      "string",
-      "null"
-    ]
-  }
-}

removedInput schema / properties / body / properties / flag / properties / completedDateTime / type
```
Removed value: -"object"
```

changedInput schema / properties / body / properties / flag / properties / dueDateTime / $ref

Previous value: -"#/properties/body/properties/flag/properties/completedDateTime"New value: +"#/$defs/def0"

changedInput schema / properties / body / properties / flag / properties / startDateTime / $ref

Previous value: -"#/properties/body/properties/flag/properties/completedDateTime"New value: +"#/$defs/def0"

addedInput schema / properties / body / properties / from / $ref
```
Added value: +"#/$defs/def1"
```
removedInput schema / properties / body / properties / from / additionalProperties
```
Removed value: -true
```

removedInput schema / properties / body / properties / from / properties

Removed value: -{
-  "emailAddress": {
-    "additionalProperties": true,
-    "properties": {
-      "address": {
-        "description": "The email address of the person or entity.",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "name": {
-        "description": "The display name of the person or entity.",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  }
-}

removedInput schema / properties / body / properties / from / type
```
Removed value: -"object"
```

changedInput schema / properties / body / properties / toRecipients / items / $ref

Previous value: -"#/properties/body/properties/from"New value: +"#/$defs/def1"

Addedv0.131.2Jul 18, 2026
Removedv0.131.2Jul 18, 2026

Changed1 schema field changedv0.131.1Jul 11, 2026

addedInput schema / properties / confirm

Added value: +{
+  "description": "For destructive operations when the confirm gate is enabled (MS365_MCP_REQUIRE_CONFIRM=true; off by default). Set to true only after the user has explicitly approved this action. When the gate is on, calls without confirm: true return { error: \"confirmation_required\" } without touching user data.",
+  "type": "boolean"
+}

Addedv0.114.0May 28, 2026
Removedv0.112.2May 22, 2026
Addedv0.110.0May 18, 2026
Removedv0.108.0May 15, 2026

Changed20 schema fields changedv0.96.0May 4, 2026

addedInput schema / properties / body / properties / bccRecipients / items / $ref
```
Added value: +"#/properties/body/properties/from"
```
removedInput schema / properties / body / properties / bccRecipients / items / additionalProperties
```
Removed value: -false
```

removedInput schema / properties / body / properties / bccRecipients / items / properties

Removed value: -{
-  "emailAddress": {
-    "additionalProperties": false,
-    "properties": {
-      "address": {
-        "description": "The email address of the person or entity.",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "name": {
-        "description": "The display name of the person or entity.",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  }
-}

removedInput schema / properties / body / properties / bccRecipients / items / type
```
Removed value: -"object"
```
changedInput schema / properties / body / properties / body / additionalProperties
```
Previous value: -falseNew value: +true
```

changedInput schema / properties / body / properties / ccRecipients / items / $ref

Previous value: -"#/properties/body/properties/bccRecipients/items"New value: +"#/properties/body/properties/from"

changedInput schema / properties / body / properties / flag / additionalProperties
```
Previous value: -falseNew value: +true
```
changedInput schema / properties / body / properties / flag / properties / completedDateTime / additionalProperties
```
Previous value: -falseNew value: +true
```

removedInput schema / properties / body / properties / from / $ref

Removed value: -"#/properties/body/properties/bccRecipients/items"

addedInput schema / properties / body / properties / from / additionalProperties
```
Added value: +true
```

addedInput schema / properties / body / properties / from / properties

Added value: +{
+  "emailAddress": {
+    "additionalProperties": true,
+    "properties": {
+      "address": {
+        "description": "The email address of the person or entity.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "description": "The display name of the person or entity.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+}

addedInput schema / properties / body / properties / from / type
```
Added value: +"object"
```

changedInput schema / properties / body / properties / internetMessageHeaders / description

Previous value: -"A collection of message headers defined by RFC5322. The set includes message headers indicating the network path taken by a message from the sender to the recipient. It can also contain custom message headers that hold app data for the message.  Returned only on applying a $select query option. Read-only."New value: +"A collection of message headers defined by RFC5322. The set includes message headers indicating the network path taken by a message from the sender to the recipient. It can also contain custom message headers that hold app data for the message.  Requires $select to retrieve. Read-only."

changedInput schema / properties / body / properties / internetMessageHeaders / items / additionalProperties
```
Previous value: -falseNew value: +true
```

removedInput schema / properties / body / properties / isRead

Removed value: -{
-  "description": "Indicates whether the message has been read.",
-  "type": [
-    "boolean",
-    "null"
-  ]
-}

removedInput schema / properties / body / properties / isReadReceiptRequested

Removed value: -{
-  "description": "Indicates whether a read receipt is requested for the message.",
-  "type": [
-    "boolean",
-    "null"
-  ]
-}

addedInput schema / properties / body / properties / multiValueExtendedProperties

Added value: +{
+  "description": "The collection of multi-value extended properties defined for the message. Nullable.",
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "id": {
+        "description": "The unique identifier for an entity. Read-only.",
+        "type": "string"
+      },
+      "value": {
+        "description": "A collection of property values.",
+        "items": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "type": "array"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

removedInput schema / properties / body / properties / parentFolderId

Removed value: -{
-  "description": "The unique identifier for the message's parent mailFolder.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

addedInput schema / properties / body / properties / singleValueExtendedProperties

Added value: +{
+  "description": "The collection of single-value extended properties defined for the message. Nullable.",
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "id": {
+        "description": "The unique identifier for an entity. Read-only.",
+        "type": "string"
+      },
+      "value": {
+        "description": "A property value.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / body / properties / toRecipients

Added value: +{
+  "description": "The To: recipients for the message.",
+  "items": {
+    "$ref": "#/properties/body/properties/from"
+  },
+  "type": "array"
+}

First observedv0.31.0Jan 27, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The key behavioral fact — the message is persisted as a draft and not delivered — is stated, which is more than the annotations convey. With destructiveHint=true declared on what is effectively a create operation, the description does not explain the confirm gate, required scopes, or what happens to the created object; it only partially covers the mutation profile.

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?

Three tight sentences, front-loaded with the action and destination, with the not-sent caveat placed where it matters. No redundant restatement of the title beyond the opening clause.

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?

For a mutation tool with no output schema, an agent is left unsure what comes back (draft ID?) needed to later send it, and the confirm-gate behavior is only in the schema. Adequate but with a real gap around follow-up actions.

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 75%, so the schema already carries most field meaning. The description enumerates subject, body, toRecipients, ccRecipients and importance but omits bccRecipients, attachments, and the confirm/includeHeaders/excludeResponse controls, and adds no syntax or formatting guidance beyond the schema.

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 and resource ('Create a draft Outlook email message') plus the destination ('signed-in user's Drafts folder'), which distinguishes it from the send-* siblings. It does not explicitly differentiate from create-reply-draft or create-forward-draft, though the 'set subject, body, recipients' framing implies a from-scratch draft.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says the draft is saved and not sent, and routes to 'send-mail' for direct sending versus sending the draft afterwards. Clear use context, but it never names the actual sibling tools (send-draft-message, create-reply-draft, create-forward-draft) an agent would have to choose between.

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

Deploy Server

create-draft-email

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools