Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

create-contact-in-folder

create-contact-in-folder
Destructive

Add a contact to a specific Outlook folder using Microsoft Graph. Provide the folder ID and contact data to place the contact exactly where needed.

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.

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.
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. 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. Addedv0.105.0

TDQS

A4/5.0
Behavior2/5

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

The annotations mark this as destructiveHint: true, but the description describes a creation operation ('Add a contact') which is not destructive. This contradiction obscures the actual side effects. The description also does not disclose any other behavioral traits such as required permissions or response behavior beyond what the schema already states, so transparency is poor.

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?

The description is compact and well-structured, consisting of two concise sentences plus a brief tip. It avoids redundancy and front-loads the core action and target, followed by usage differentiation and a retrieval hint. No filler or unnecessary details are present.

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 create operation with no output schema, the description covers the essential context: what the tool does, when to use it over the alternative, and how to supply the necessary parameters. It lacks explicit mention of success/failure response or side effects, but given the simplicity and existing schema documentation, it is nearly complete. The contradiction with the destructive hint slightly reduces completeness.

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?

The description adds meaning to the 'contactFolderId' parameter by clarifying the naming convention ('Pass it under the name 'contactFolderId', not as 'id'') and referencing the source of the value. It also summarizes the 'body' parameter as a contact resource. However, for the 'confirm', 'includeHeaders', and 'excludeResponse' parameters, the description offers no additional insight beyond the schema descriptions, which are already present.

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 clearly states the action ('Add'), the target ('a contact'), and the location ('to the root Contacts folder or to the contacts endpoint of another contact folder'). It also names the sibling tool it differentiates from, making the purpose unambiguous.

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?

It explicitly contrasts with create-outlook-contact, stating when to use this tool versus the alternative ('writes to the default folder only; use this when organizing contacts into named folders'). It also provides a retrieval hint ('Get the folder id via list-contact-folders').

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