Skip to main content
Glama
Microsoft 365 MCP Server

Microsoft 365 MCP Server

by Softeria

update-outlook-contact

update-outlook-contact
Destructive

Update an Outlook contact's properties by contact ID. Include the full emailAddresses array when changing it, because the array is replaced entirely.

Instructions

Update the properties of a contact object.

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "body": "<body>",
      "contactId": "<contactId>"
    },
    "name": "update-outlook-contact"
  }
}

Input 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.

  1. Changed3 schema fields changedv0.176.1
    • removedInput schema / properties / body / properties / birthday / description
      Removed value: -"The contact's birthday. The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z"
    • removedInput schema / properties / body / properties / createdDateTime / description
      Removed value: -"The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z"
    • removedInput schema / properties / body / properties / lastModifiedDateTime / description
      Removed value: -"The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z"
  2. 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"
  3. Addedv0.134.4
  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. 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"
      +}
  11. First observedv0.31.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered externally. The description adds genuine behavioral value by warning that emailAddresses is replaced entirely rather than merged — a non-obvious mutation semantic. It still omits whether other fields are partial-patch or full-replace, and says nothing about the confirm gate or error behavior.

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 lines, the core action first and the caveat second. Nothing is padded and the tip is exactly the kind of detail an agent would otherwise get wrong.

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 destructive, deeply nested mutation of a Graph contact object, the description covers only one of many gotchas. Annotations carry the safety signal and the schema documents most fields, but the partial-vs-full update semantics for the rest of the body remain undocumented.

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 80%, so the baseline is 3. The emailAddresses replacement tip adds real meaning beyond the schema's bare 'The contact's email addresses' description, but contactId, confirm, includeHeaders and excludeResponse get no coverage in the description at all.

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?

States a specific verb and resource ('Update the properties of a contact object'), which clearly separates it from create-outlook-contact, get-outlook-contact and delete-outlook-contact listed as siblings. It does not explicitly name those siblings, so it stops short of a 5.

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?

No guidance on when to use this versus the sibling contact tools, and no prerequisites (e.g. that contactId must come from a prior get/list call). The only usage-flavored content is a tip about how the emailAddresses field behaves, not about when to invoke the tool.

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