Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

update-outlook-contact

update-outlook-contact
Destructive

Update an existing Outlook contact's properties in Microsoft 365. Change names, phones, emails, addresses, or birthday; when updating email addresses, include all addresses to avoid losing existing ones.

Instructions

Update the properties of a contact object.

💡 TIP: emailAddresses array is replaced entirely — include all addresses, not just new ones.

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.
contactIdYesValue for the 'contactId' path segment. Pass it under the name 'contactId', not as 'id'. Use the 'id' field of the contact object as returned by Microsoft Graph.
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": {
-      "city": {
-        "description": "The city.",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "countryOrRegion": {
-        "description": "The country or region. It's a free-format string value, for example, 'United States'.",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "postalCode": {
-        "description": "The postal code.",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "state": {
-        "description": "The state.",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "street": {
-        "description": "The street.",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  }
-}
    • removedInput schema / properties / body / properties / businessAddress / $ref
      Removed value: -"#/$defs/def0"
    • addedInput schema / properties / body / properties / businessAddress / additionalProperties
      Added value: +true
    • addedInput schema / properties / body / properties / businessAddress / properties
      Added value: +{
+  "city": {
+    "description": "The city.",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "countryOrRegion": {
+    "description": "The country or region. It's a free-format string value, for example, 'United States'.",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "postalCode": {
+    "description": "The postal code.",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "state": {
+    "description": "The state.",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "street": {
+    "description": "The street.",
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}
    • addedInput schema / properties / body / properties / businessAddress / type
      Added value: +"object"
    • removedInput schema / properties / body / properties / homeAddress / $ref
      Removed value: -"#/$defs/def0"
    • addedInput schema / properties / body / properties / homeAddress / additionalProperties
      Added value: +true
    • addedInput schema / properties / body / properties / homeAddress / properties
      Added value: +{
+  "city": {
+    "description": "The city.",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "countryOrRegion": {
+    "description": "The country or region. It's a free-format string value, for example, 'United States'.",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "postalCode": {
+    "description": "The postal code.",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "state": {
+    "description": "The state.",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "street": {
+    "description": "The street.",
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}
    • addedInput schema / properties / body / properties / homeAddress / 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. Changed6 schema fields changedv0.96.0
    • changedInput schema / properties / body / properties / businessAddress / additionalProperties
      Previous value: -falseNew value: +true
    • changedInput schema / properties / body / properties / emailAddresses / items / additionalProperties
      Previous value: -falseNew value: +true
    • removedInput schema / properties / body / properties / jobTitle
      Removed value: -{
-  "description": "The contact’s job title.",
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • removedInput schema / properties / body / properties / manager
      Removed value: -{
-  "description": "The name of the contact's manager.",
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • addedInput schema / properties / body / properties / multiValueExtendedProperties
      Added value: +{
+  "description": "The collection of multi-value extended properties defined for the contact. Read-only. 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"
+}
    • addedInput schema / properties / body / properties / singleValueExtendedProperties
      Added value: +{
+  "description": "The collection of single-value extended properties defined for the contact. Read-only. 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"
+}
  10. First observedv0.31.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already mark this as destructive (destructiveHint=true) and not read-only, so the description's job is lighter. The tip about emailAddresses being replaced entirely adds valuable non-obvious behavioral context beyond what annotations or the schema description provide.

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?

Two short sentences with no filler. The core purpose is stated first, and the critical gotcha is placed immediately after, making the most important operational detail easy to notice.

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?

The description covers the main non-obvious behavior but remains minimal for a mutation tool with a large nested body schema. It does not explicitly state whether omitted properties are preserved or whether the operation is a partial update, and there is no output schema to clarify the response shape.

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 description coverage is high (80%), so the baseline is 3. The description adds meaningful semantics for the emailAddresses parameter by warning that the array is wholly replaced, which is not stated in the schema's own parameter description.

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 states a clear verb ('Update') and resource ('contact object'), which distinguishes it from create/get/delete contact siblings. It does not explicitly differentiate from update-contact-folder, but the resource is specific enough for an agent to disambiguate.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus create-outlook-contact, delete-outlook-contact, or get-outlook-contact. There is also no mention of prerequisites or cases where an update would be inappropriate.

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