Microsoft 365 MCP Server

update-mail-message

update-mail-message

Destructive

Modify an existing Outlook email by ID to mark read/unread, flag, set categories or importance, and edit draft subject, body, or recipients.

Instructions

Update an existing Outlook email message by its message ID — for example mark it read or unread (isRead), flag it (flag), change its categories, importance, or edit a draft's subject, body, or recipients.

Input Schema

TableJSON 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.
`messageId`	Yes	Value for the 'messageId' path segment. Pass it under the name 'messageId', not as 'id'. Use the 'id' field of the message object as returned by Microsoft Graph.
`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. Dates show when Glama detected each change.

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"
```

Changed15 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"

changedInput schema / properties / messageId / description

Previous value: -"Path parameter: messageId"New value: +"Value for the 'messageId' path segment. Pass it under the name 'messageId', not as 'id'. Use the 'id' field of the message object as returned by Microsoft Graph."

Changed1 schema field changedv0.131.2Jul 18, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

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
Addedv0.96.0May 4, 2026

TDQS

A3.9/5.0

Behavior3/5

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

The annotations already mark this as destructive (destructiveHint=true) and read-only=false, so the description doesn't need to restate mutation. It adds some transparency by noting that subject/body/recipients edits apply to a draft, but it does not disclose other side effects such as permanence of changes, potential confirm gate behavior, or that some fields may be read-only.

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?

A single sentence that front-loads the action and resource, then provides illustrative use cases. No wasted words or redundant repetition of schema information.

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 a large nested body schema and no output schema, the description is adequate but not rich. It explains common use cases but omits important operational context such as the confirm gate (covered in schema but not description), the fact that messageId is required, and the distinction between draft vs sent message update constraints beyond the draft mention.

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 high (80%), so the schema already documents most parameters. The description adds value by mapping examples (isRead, flag, categories, importance, subject, body, recipients) to the 'body' parameter, but it doesn't go beyond what a careful agent could infer from the schema.

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 clearly states the verb ('Update'), the resource ('existing Outlook email message'), and the key method ('by its message ID'). It lists concrete examples of updatable fields (isRead, flag, categories, importance) and even distinguishes draft-specific edits, making the tool's purpose unmistakable and distinct from siblings like delete-mail-message or move-mail-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 context: use when you need to modify an existing Outlook message's properties. It does not explicitly name alternative tools or state when not to use it, but the context is strong enough that the agent can infer the right scenario.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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