Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

create-draft-email

create-draft-email
Destructive

Creates a draft Outlook email message in the signed-in user's Drafts folder. Set subject, body, recipients, CC, and importance; the draft is saved for later review and sending.

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. Dates show when Glama detected each change.

  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 already signal a mutating readOnlyHint=false and destructiveHint=true, so the bar is lower. Beyond that, the description discloses the critical non-obvious behavior 'saved, not sent' — an agent might otherwise assume the call sends the email. This is a genuinely valuable behavioral disclosure. Remaining gaps are minor: no mention of return value, errors, or the confirm gate, but the confirm gate is documented in the schema.

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 short sentences, with the core purpose front-loaded first and the routing guidance placed last. The second sentence listing fields is mildly redundant with the rich schema, but it is still helpful as a quick summary of what the caller should worry about. No filler or repetition of annotation content.

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 tool with a large nested input schema and no output schema, the description covers the essential aspects: what is created, where it lands, what fields matter, and the saved-not-sent behavior. The main omission is that there is no explicit note about what the call returns (e.g., the created message with its id), which is useful since the output schema 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 75%, so most parameters are already documented inside the input schema itself. The description adds the context that subject, body, toRecipients, ccRecipients, and importance are the fields the caller would typically populate, but doesn't explain structural concepts such as recipient shapes or content type. That is a small reinforcement, not a substantial addition, so the baseline 3 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 states a clear verb (create) plus a precise resource (a draft Outlook message in the signed-in user's Drafts folder) and enumerates which fields can be set. It also separates itself from send-oriented tools, so an agent can distinguish it from siblings such as send-mail, send-draft-message, and create-reply-draft without opening their schemas.

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 third sentence explicitly routes the agent: 'The draft is saved, not sent — use send-mail to send a message directly, or send the draft afterwards.' That names the primary alternative with the selecting condition (the distinction between creating vs. sending). The only gap is that it doesn't name send-draft-message explicitly as the specific tool to send the draft afterwards, nor does it mention the forward/reply draft siblings, leaving a small part of the routing to inference.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Softeria/ms-365-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server