Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

update-mailbox-settings

update-mailbox-settings
Destructive

Update mailbox settings such as automatic replies (Out-of-Office), working hours, time zone, and date/time formats to reflect user preferences.

Instructions

Enable, configure, or disable one or more of the following settings as part of a user's mailboxSettings: When updating the preferred date or time format for a user, specify it in respectively, the short date or short time format. When updating the preferred time zone for a user, specify it in the Windows or Internet Assigned Numbers Authority (IANA) time zone (also known as Olson time zone) format. You can also further customize the time zone as shown in example 2 below.

šŸ’” TIP: Updates mailbox settings. Common use: configure Out-of-Office (automatic replies). Body example: { automaticRepliesSetting: { status: 'scheduled', scheduledStartDateTime: { dateTime: '2026-03-28T17:00:00', timeZone: 'Eastern Standard Time' }, scheduledEndDateTime: { dateTime: '2026-04-01T08:00:00', timeZone: 'Eastern Standard Time' }, internalReplyMessage: 'I am OOO.', externalReplyMessage: 'I am out of office.' } }. Status values: disabled, alwaysEnabled, scheduled.

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. Changed9 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"
-  }
-}
    • removedInput schema / properties / body / properties / automaticRepliesSetting / properties / scheduledEndDateTime / $ref
      Removed value: -"#/$defs/def0"
    • addedInput schema / properties / body / properties / automaticRepliesSetting / properties / scheduledEndDateTime / additionalProperties
      Added value: +true
    • addedInput schema / properties / body / properties / automaticRepliesSetting / properties / scheduledEndDateTime / 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 / automaticRepliesSetting / properties / scheduledEndDateTime / type
      Added value: +"object"
    • removedInput schema / properties / body / properties / automaticRepliesSetting / properties / scheduledStartDateTime / $ref
      Removed value: -"#/$defs/def0"
    • addedInput schema / properties / body / properties / automaticRepliesSetting / properties / scheduledStartDateTime / additionalProperties
      Added value: +true
    • addedInput schema / properties / body / properties / automaticRepliesSetting / properties / scheduledStartDateTime / 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 / automaticRepliesSetting / properties / scheduledStartDateTime / type
      Added value: +"object"
  2. Addedv0.134.4
  3. Removedv0.131.2
  4. 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"
+}
  5. Addedv0.114.0
  6. Removedv0.112.2
  7. Addedv0.110.0
  8. Removedv0.108.0
  9. Addedv0.96.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already mark the tool as non-readOnly and destructive, so the description does not need to belabor that modifying mailbox settings has side effects. It does add useful context about supported formats for time zone and date/time values, but it does not explain what happens to existing settings that are omitted from the request or what the response will include.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description includes useful example and format guidance, but it is not tightly written. The 'TIP' sentence largely restates the tool name, the status values duplicate the schema enum, and 'as shown in example 2 below' refers to content that is not present, adding unnecessary noise.

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 tool with nested objects and no output schema, the description provides one strong common-use example but insufficient general coverage of other settings in the body. It does not describe the response format, behavior when partial settings are updated, or relationship to get-mailboxSettings, leaving the agent to rely on the schema for completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%, and the description adds real value beyond the schema by explaining short date/time format constraints, Windows/IANA time zone requirements, and providing a concrete automaticRepliesSetting JSON example with valid statuses. It does not cover all nested fields like workingHours or language, but the schema already describes those reasonably well.

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?

The description opens with specific verbs ('Enable, configure, or disable') tied to mailbox settings, which makes the operation clear and distinguishes it from read-only siblings like get-mailbox-settings. However, it does not explicitly enumerate all the settings it can update, and its sibling differentiation is only implied by the name.

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

Usage Guidelines3/5

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

The description gives a common use case ('configure Out-of-Office') and a concrete body example, which helps an agent understand a realistic invocation. It does not explicitly state when to choose this tool over alternatives, nor does it mention related reading tool like get-mailbox-settings, so the usage guidance remains implicit.

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