Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

create-outlook-contact

create-outlook-contact
Destructive

Add a contact to Outlook's root Contacts folder or a selected contact folder. Use it to store names, email addresses, phone numbers, and other details via Microsoft 365.

Instructions

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

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
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. 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"
+}
  10. First observedv0.31.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already signal a non-read-only, destructive mutation, so the description is not expected to repeat that. It adds the useful scoping detail of root vs other folder, though it does not mention idempotency, confirmation behavior, or side effects beyond what the confirm parameter already covers.

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 one concise, front-loaded sentence with no filler. It communicates the core action and target in under 20 words, and every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The input schema is large and nested, and there is an overlapping sibling create-contact-in-folder, yet the description never explains how to target a non-root folder or what distinguishes this variant. There is also no output schema and no mention of return values or required body fields, leaving important call details to inference.

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 no parameter-level meaning, but the schema carries 75% coverage, including rich descriptions for the nested body properties and the confirm/includeHeaders/excludeResponse parameters. Since the schema already documents the parameters sufficiently, the description does not need to restate them.

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 states the exact operation ('Add a contact') and the two target locations: the root Contacts folder or another contact folder's contacts endpoint. It is clear about the resource and action, but it does not explicitly distinguish this from the sibling create-contact-in-folder, so it is not fully differentiated.

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?

There is no guidance on when to choose this tool over create-contact-in-folder or update-outlook-contact, and no mention of prerequisites or exclusions. The folder-target wording provides only a weak contextual hint for routing an agent.

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