Skip to main content
Glama
Microsoft 365 MCP Server

Microsoft 365 MCP Server

by Softeria

create-contact-child-folder

create-contact-child-folder
Destructive

Creates a child contact folder under a specified parent folder or the default contacts folder. Use it to organize contacts into sub-folders and obtain the new folder's id for further operations.

Instructions

Create a new contactFolder as a child of a specified folder. You can also create a new contactFolder under the user's default contact folder.

šŸ’” TIP: Creates a sub-folder under an existing contact folder. Body: { displayName: 'Sub-folder name' }. Use list-contact-folders to discover the parent id. The returned contactFolder has its own id usable with update-contact-folder, delete-contact-folder, list-contact-folder-contacts, and create-contact-in-folder — contactFolder ids are mailbox-unique regardless of nesting depth.

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": "create-contact-child-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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the returned folder has its own id usable with update/delete/list/create-contact-in-folder, and ids are mailbox-unique regardless of nesting depth.

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?

Purpose is front-loaded in the first sentence and the TIP block delivers practical extras. There's mild redundancy between 'as a child of a specified folder' and 'Creates a sub-folder under an existing contact folder', but overall it's efficient.

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?

It covers what gets created, how to find the parent, and what the returned id enables downstream — enough to call correctly even without an output schema. It omits mention of the confirm gate that the schema exposes for destructive operations, a minor gap.

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?

With 80% schema coverage the baseline is 3, and the description adds a concrete body example ('Body: { displayName: Sub-folder name }') plus guidance to obtain the parent id via list-contact-folders. It doesn't address confirm/includeHeaders/excludeResponse, but those are documented in 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 states a specific verb and resource — 'Create a new contactFolder as a child of a specified folder' — and distinguishes it from sibling create-contact-folder (top-level) and create-contact-in-folder (contacts inside a folder) by emphasizing the child/sub-folder relationship.

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 names list-contact-folders as the discovery tool for the parent id and explains the default-folder alternative, giving an agent clear routing. It doesn't explicitly state when NOT to use this versus create-contact-folder, which keeps it short of a 5.

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