Skip to main content
Glama
Microsoft 365 MCP Server

Microsoft 365 MCP Server

by Softeria

update-contact-folder

update-contact-folder
Destructive

Rename or move a Microsoft 365 contact folder by updating its display name or parent folder ID.

Instructions

Update the properties of contactfolder object.

šŸ’” TIP: Updates a contact folder. Body: { displayName?: 'New name', parentFolderId?: '' } — both displayName (rename) and parentFolderId (move) are writable. The default 'Contacts' folder may not be renameable. Get the folder id via list-contact-folders.

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>",
      "contactFolderId": "<contactFolderId>"
    },
    "name": "update-contact-folder"
  }
}

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.
includeHeadersNoInclude response headers (including ETag) in the response metadata
contactFolderIdYesValue for the 'contactFolderId' path segment. Pass it under the name 'contactFolderId', not as 'id'. Use the 'id' field of the contact folder object as returned by Microsoft Graph.
excludeResponseNoExclude the full response body and only return success or failure indication

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed44 schema fields changedv0.176.1
    • changedInput schema / $defs / def0 / properties / multiValueExtendedProperties / items / $ref
      Previous value: -"#/$defs/def3"New value: +"#/$defs/def5"
    • removedInput schema / $defs / def1 / 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"
    • changedInput schema / $defs / def1 / properties / businessAddress / $ref
      Previous value: -"#/$defs/def2"New value: +"#/$defs/def8"
    • addedInput schema / $defs / def1 / properties / businessPhones / items / $ref
      Added value: +"#/$defs/def9"
    • removedInput schema / $defs / def1 / properties / businessPhones / items / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
    • addedInput schema / $defs / def1 / properties / categories / items / $ref
      Added value: +"#/$defs/def7"
    • removedInput schema / $defs / def1 / properties / categories / items / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
    • addedInput schema / $defs / def1 / properties / children / items / $ref
      Added value: +"#/$defs/def10"
    • removedInput schema / $defs / def1 / properties / children / items / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
    • removedInput schema / $defs / def1 / 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"
    • addedInput schema / $defs / def1 / properties / emailAddresses / items / $ref
      Added value: +"#/$defs/def11"
    • removedInput schema / $defs / def1 / properties / emailAddresses / items / additionalProperties
      Removed value: -true
    • removedInput schema / $defs / def1 / properties / emailAddresses / items / properties
      Removed value: -{
      -  "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"
      -    ]
      -  }
      -}
    • removedInput schema / $defs / def1 / properties / emailAddresses / items / type
      Removed value: -"object"
    • changedInput schema / $defs / def1 / properties / homeAddress / $ref
      Previous value: -"#/$defs/def2"New value: +"#/$defs/def8"
    • addedInput schema / $defs / def1 / properties / homePhones / items / $ref
      Added value: +"#/$defs/def2"
    • removedInput schema / $defs / def1 / properties / homePhones / items / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
    • addedInput schema / $defs / def1 / properties / imAddresses / items / $ref
      Added value: +"#/$defs/def3"
    • removedInput schema / $defs / def1 / properties / imAddresses / items / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
    • removedInput schema / $defs / def1 / 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"
    • changedInput schema / $defs / def1 / properties / multiValueExtendedProperties / items / $ref
      Previous value: -"#/$defs/def3"New value: +"#/$defs/def5"
    • addedInput schema / $defs / def10
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / $defs / def11
      Added value: +{
      +  "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 / $defs / def12
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / $defs / def13
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / $defs / def14
      Added value: +{
      +  "type": "boolean"
      +}
    • removedInput schema / $defs / def2 / additionalProperties
      Removed value: -true
    • removedInput schema / $defs / def2 / properties
      Removed 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"
      -    ]
      -  }
      -}
    • changedInput schema / $defs / def2 / type
      Previous value: -"object"New value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / $defs / def3 / additionalProperties
      Removed value: -true
    • removedInput schema / $defs / def3 / properties
      Removed value: -{
      -  "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"
      -  }
      -}
    • changedInput schema / $defs / def3 / type
      Previous value: -"object"New value: +[
      +  "string",
      +  "null"
      +]
    • addedInput schema / $defs / def5
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "id": {
      +      "description": "The unique identifier for an entity. Read-only.",
      +      "type": "string"
      +    },
      +    "value": {
      +      "description": "A collection of property values.",
      +      "items": {
      +        "$ref": "#/$defs/def6"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / $defs / def6
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / $defs / def7
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / $defs / def8
      Added value: +{
      +  "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"
      +}
    • addedInput schema / $defs / def9
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedInput schema / properties / body / properties / multiValueExtendedProperties / items / $ref
      Previous value: -"#/$defs/def3"New value: +"#/$defs/def5"
    • addedInput schema / properties / confirm / allOf
      Added value: +[
      +  {
      +    "$ref": "#/$defs/def12"
      +  }
      +]
    • removedInput schema / properties / confirm / type
      Removed value: -"boolean"
    • addedInput schema / properties / excludeResponse / allOf
      Added value: +[
      +  {
      +    "$ref": "#/$defs/def13"
      +  }
      +]
    • removedInput schema / properties / excludeResponse / type
      Removed value: -"boolean"
    • addedInput schema / properties / includeHeaders / allOf
      Added value: +[
      +  {
      +    "$ref": "#/$defs/def14"
      +  }
      +]
    • removedInput schema / properties / includeHeaders / type
      Removed value: -"boolean"
  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.105.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true. The description adds useful behavioral detail beyond that: which properties are writable, that parentFolderId performs a move, and that the default 'Contacts' folder may not be renameable. It does not repeat the confirm-gate behavior, but that 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?

The description is short and front-loaded, with the key body shape and caveats in the TIP. There is minor redundancy between 'Update the properties of contactfolder object' and 'TIP: Updates a contact folder,' but no significant wasted 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 complex nested schema with annotations and no output schema, the description covers the critical practical details: writable fields, rename/move semantics, the default-folder caveat, and how to get the folder ID. The confirm gate and other response controls are left to the schema, which is acceptable.

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 high at 80%, so the baseline is 3. The description adds valuable meaning by clarifying that only displayName and parentFolderId are writable in the body, despite many read-only fields in the schema, and by pointing the agent to list-contact-folders to obtain the contactFolderId.

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 gives a clear verb and resource: 'Update the properties of contactfolder object' and 'Updates a contact folder.' This distinguishes it from most siblings by resource type, though it does not explicitly contrast with update-outlook-contact or other update-* tools.

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?

It tells the agent when to use the tool: renaming via displayName or moving via parentFolderId. It also includes the prerequisite 'Get the folder id via list-contact-folders' and a caveat that the default 'Contacts' folder may not be renameable, but it does not explicitly state when not to use it or name a direct alternative.

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