Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create-draft-email

create-draft-email
Destructive

Create a draft Outlook email in your Drafts folder with subject, body, recipients, and importance. Save it for later editing instead of sending it immediately.

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

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
confirmNoFor 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.
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed29 schema fields changedv0.145.2
    • 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"
  2. Changed14 schema fields changedv0.134.4
    • 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"
  3. Addedv0.131.2
  4. Removedv0.131.2
  5. Changed1 schema field changedv0.131.1
    • 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"
+}
  6. Addedv0.114.0
  7. Removedv0.112.2
  8. Addedv0.110.0
  9. Removedv0.108.0
  10. Changed20 schema fields changedv0.96.0
    • 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"
+}
  11. First observedv0.31.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, so the write nature is already known. The description adds genuine behavioral context beyond that: the draft is persisted to the Drafts folder and is NOT sent, which materially affects how an agent sequences this call. Given annotations already carry the safety profile, this is solid added value without contradicting anything.

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 tightly packed sentences: purpose and location first, then settable fields, then the critical save-vs-send disambiguation. No filler or redundancy; every sentence earns its place. Could perhaps front-load the 'not sent' clarification even earlier, but the structure is efficient.

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?

For a draft-creation tool with annotations covering the write/destructive profile, the description captures the essential behavior: it saves a draft, names the settable fields, and disambiguates from sending. Optional fields like attachments and bcc are absent but are documented in the schema body nested properties. The confirm-gate parameter is self-documented in the schema, so no gap there. An agent can call this correctly with the given information.

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 coverage is 75% (moderately high), so the schema documents most parameters. The description names the key message fields (subject, body, toRecipients, ccRecipients, importance) which maps to nested schema properties and adds modest orientation for an agent. It does not add format or syntax details beyond the schema, so a 3 baseline is appropriate.

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 uses a specific verb+resource+scope: 'Create a draft Outlook email message in the signed-in user's Drafts folder.' It names the settable fields (subject, body, toRecipients, ccRecipients, importance) and explicitly contrasts itself with send-mail by stating the draft is saved, not sent. An agent can immediately tell what this tool does and how it differs from send-mail/send-draft-message.

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?

The description gives clear when-to-use context: it states the draft is not sent and points to send-mail as the alternative for direct sending ('use send-mail to send a message directly, or send the draft afterwards'). However, among the large sibling set there are create-forward-draft, create-reply-draft, and create-reply-all-draft, which are not explicitly excluded; the phrase 'draft Outlook email message' only indirectly implies a fresh draft. Some exclusion guidance for those variants would push this to 5.

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