Microsoft 365 MCP Server

create-planner-task

create-planner-task

Destructive

Create a new task in a Microsoft Planner plan with details such as title, bucket, priority, assignments, and due date to organize team work.

Instructions

Create a new plannerTask.

Input Schema

Name	Required	Description
`body`	Yes
`confirm`	No	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.
`includeHeaders`	No	Include response headers (including ETag) in the response metadata
`excludeResponse`	No	Exclude the full response body and only return success or failure indication

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.176.1Oct 29, 2026

removedInput schema / properties / body / properties / activeChecklistItemCount / description

Removed value: -"Number of checklist items with value set to false, representing incomplete items."

removedInput schema / properties / body / properties / checklistItemCount / description
```
Removed value: -"Number of checklist items that are present on the task."
```

removedInput schema / properties / body / properties / completedDateTime / description

Removed value: -"Read-only. Date and time at which the 'percentComplete' of the task is set to '100'. 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: -"Read-only. Date and time at which the task is created. 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 / dueDateTime / description

Removed value: -"Date and time at which the task is due. 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 / percentComplete / description

Removed value: -"Percentage of task completion. When set to 100, the task is considered completed."

removedInput schema / properties / body / properties / priority / description

Removed value: -"Priority of the task. The valid range of values is between 0 and 10, with the increasing value being lower priority (0 has the highest priority and 10 has the lowest priority).  Currently, Planner interprets values 0 and 1 as 'urgent', 2, 3 and 4 as 'important', 5, 6, and 7 as 'medium', and 8, 9, and 10 as 'low'.  Additionally, Planner sets the value 1 for 'urgent', 3 for 'important', 5 for 'medium', and 9 for 'low'."

removedInput schema / properties / body / properties / referenceCount / description
```
Removed value: -"Number of external references that exist on the task."
```

removedInput schema / properties / body / properties / startDateTime / description

Removed value: -"Date and time at which the task starts. 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"

Changed15 schema fields changedv0.145.2Aug 22, 2026

removedInput schema / $defs

Removed value: -{
-  "def0": {
-    "additionalProperties": true,
-    "properties": {
-      "application": {
-        "$ref": "#/$defs/def1"
-      },
-      "device": {
-        "$ref": "#/$defs/def1"
-      },
-      "user": {
-        "$ref": "#/$defs/def1"
-      }
-    },
-    "type": "object"
-  },
-  "def1": {
-    "additionalProperties": true,
-    "properties": {
-      "displayName": {
-        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "id": {
-        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  },
-  "def2": {
-    "enum": [
-      "automatic",
-      "noPreview",
-      "checklist",
-      "description",
-      "reference"
-    ],
-    "type": "string"
-  }
-}

removedInput schema / properties / body / properties / completedBy / $ref
```
Removed value: -"#/$defs/def0"
```
addedInput schema / properties / body / properties / completedBy / additionalProperties
```
Added value: +true
```

addedInput schema / properties / body / properties / completedBy / properties

Added value: +{
+  "application": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "device": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "user": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+}

addedInput schema / properties / body / properties / completedBy / type
```
Added value: +"object"
```
removedInput schema / properties / body / properties / createdBy / $ref
```
Removed value: -"#/$defs/def0"
```
addedInput schema / properties / body / properties / createdBy / additionalProperties
```
Added value: +true
```

addedInput schema / properties / body / properties / createdBy / properties

Added value: +{
+  "application": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "device": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "user": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+}

addedInput schema / properties / body / properties / createdBy / type
```
Added value: +"object"
```
removedInput schema / properties / body / properties / details / properties / previewType / $ref
```
Removed value: -"#/$defs/def2"
```

addedInput schema / properties / body / properties / details / properties / previewType / enum

Added value: +[
+  "automatic",
+  "noPreview",
+  "checklist",
+  "description",
+  "reference"
+]

addedInput schema / properties / body / properties / details / properties / previewType / type
```
Added value: +"string"
```
removedInput schema / properties / body / properties / previewType / $ref
```
Removed value: -"#/$defs/def2"
```

addedInput schema / properties / body / properties / previewType / enum

Added value: +[
+  "automatic",
+  "noPreview",
+  "checklist",
+  "description",
+  "reference"
+]

addedInput schema / properties / body / properties / previewType / type
```
Added value: +"string"
```

Changed10 schema fields changedv0.134.4Jul 28, 2026

addedInput schema / $defs

Added value: +{
+  "def0": {
+    "additionalProperties": true,
+    "properties": {
+      "application": {
+        "$ref": "#/$defs/def1"
+      },
+      "device": {
+        "$ref": "#/$defs/def1"
+      },
+      "user": {
+        "$ref": "#/$defs/def1"
+      }
+    },
+    "type": "object"
+  },
+  "def1": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "def2": {
+    "enum": [
+      "automatic",
+      "noPreview",
+      "checklist",
+      "description",
+      "reference"
+    ],
+    "type": "string"
+  }
+}

addedInput schema / properties / body / properties / completedBy / $ref
```
Added value: +"#/$defs/def0"
```
removedInput schema / properties / body / properties / completedBy / additionalProperties
```
Removed value: -true
```

removedInput schema / properties / body / properties / completedBy / properties

Removed value: -{
-  "application": {
-    "additionalProperties": true,
-    "properties": {
-      "displayName": {
-        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "id": {
-        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  },
-  "device": {
-    "$ref": "#/properties/body/properties/completedBy/properties/application"
-  },
-  "user": {
-    "$ref": "#/properties/body/properties/completedBy/properties/application"
-  }
-}

removedInput schema / properties / body / properties / completedBy / type
```
Removed value: -"object"
```

changedInput schema / properties / body / properties / createdBy / $ref

Previous value: -"#/properties/body/properties/completedBy"New value: +"#/$defs/def0"

addedInput schema / properties / body / properties / details / properties / previewType / $ref
```
Added value: +"#/$defs/def2"
```

removedInput schema / properties / body / properties / details / properties / previewType / enum

Removed value: -[
-  "automatic",
-  "noPreview",
-  "checklist",
-  "description",
-  "reference"
-]

removedInput schema / properties / body / properties / details / properties / previewType / type
```
Removed value: -"string"
```

changedInput schema / properties / body / properties / previewType / $ref

Previous value: -"#/properties/body/properties/details/properties/previewType"New value: +"#/$defs/def2"

Changed1 schema field changedv0.131.2Jul 18, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

Changed1 schema field changedv0.131.1Jul 11, 2026

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"
+}

Addedv0.114.0May 28, 2026
Removedv0.112.2May 22, 2026
Addedv0.110.0May 18, 2026
Removedv0.108.0May 15, 2026
Changed10 schema fields changedv0.96.0May 4, 2026
- changedInput schema / properties / body / properties / appliedCategories / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / assignedToTaskBoardFormat / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / assignedToTaskBoardFormat / properties / orderHintsByAssignee / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / assignments / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / bucketTaskBoardFormat / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / completedBy / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / completedBy / properties / application / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / details / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / details / properties / checklist / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / details / properties / references / additionalProperties
```
Previous value: -falseNew value: +true
```
First observedv0.31.0Jan 27, 2026

TDQS

C2.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is partly covered elsewhere. The description adds nothing about the confirm gate (even though a `confirm` parameter exists), what gets created, or side effects; for a mutation tool with nested payloads this is a real gap, though not a contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no waste, but the brevity is under-specification rather than efficiency: there is no front-loaded detail an agent could act on beyond the name.

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?

Given a required nested `body` object with many read-only fields, no output schema, and a confirm-gate parameter, the description is far too thin to guide a correct call. It supplies none of the operational context the structured fields don't already state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%, below the high-coverage baseline, and the description names no parameters at all. It never mentions that `body` is required or that planId/title are the meaningful fields, leaving the agent to reverse-engineer the large nested payload itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence names a verb and resource ('Create a new plannerTask'), so the action is identifiable, but it does no more than restate the tool name/title. It gives no clue how it differs from create-planner-plan, create-planner-bucket, or create-todo-task in the sibling list.

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 use this versus update-planner-task or create-todo-task, and no mention of prerequisites such as needing an existing planId or a bucket that belongs to that plan. The agent must infer everything from the schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

create-planner-task

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools