Skip to main content
Glama
Microsoft 365 MCP Server

Microsoft 365 MCP Server

by Softeria

create-contact-in-folder

create-contact-in-folder
Destructive

Add a contact to a specific Microsoft 365 contact folder instead of the default Contacts folder. Use the folder ID to keep contacts organized in named folders.

Instructions

Add a contact to the root Contacts folder or to the contacts endpoint of another contact folder.

šŸ’” TIP: Creates a contact inside a specific folder (instead of the default Contacts folder). Body is a contact resource: { givenName, surname, displayName, emailAddresses: [{ address, name }], businessPhones: [], mobilePhone, jobTitle, companyName, ... }. The existing create-outlook-contact (POST /me/contacts) writes to the default folder only; use this when organizing contacts into named folders. 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": "create-contact-in-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. 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. Addedv0.105.0

TDQS

A4.5/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, so the safety profile is covered; the description adds real context beyond that: the contact is created inside an existing folder, the folder is not created here, and the folder id must come from list-contact-folders. It does not mention the confirm gate or error/response behavior, but those live in the schema, so this is strong without being exhaustive.

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?

Front-loaded with the core action, then a clearly marked TIP block containing the useful detail; no filler sentences. Slight redundancy between the first sentence and the TIP's restatement of 'creates a contact inside a specific folder', but the size is justified by the complexity of the nested body.

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 mutation tool with a deeply nested body and no output schema, the description covers the action, the folder-scoping semantics, the sibling alternative, and the folder-id source. What remains unsaid (confirm gate behavior, response shape, failure modes) is documented in the schema, so an agent has enough to call it correctly.

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 (~80%), so the schema carries most parameter documentation, but the description adds a compact body shape summary (givenName, surname, displayName, emailAddresses as {address, name}, businessPhones, jobTitle, companyName) and clarifies how to source contactFolderId. Minor value-add beyond structured fields, though 'mobilePhone' in the tip is not a listed schema property.

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?

States a specific verb and resource ('Add a contact') plus a precise scope ('to the root Contacts folder or to the contacts endpoint of another contact folder'), and explicitly distinguishes itself from create-outlook-contact. An agent can tell exactly which contact-creation tool this is without reading the schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use rule ('use this when organizing contacts into named folders'), names the alternative (create-outlook-contact POST /me/contacts) and its limitation (default folder only), and tells the agent where to obtain the required folder id (list-contact-folders). All routing decisions are resolved in the description.

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