Microsoft 365 MCP Server

update-planner-task

update-planner-task

Destructive

Modify existing Planner tasks by changing title, priority, due dates, assignments, or checklist items. Requires the task ID and ETag to apply changes.

Instructions

Update the properties of plannerTask object.

💡 TIP: CRITICAL: Requires If-Match header with the task's @odata.etag value, otherwise returns 412 Precondition Failed. Get the ETag from get-planner-task with includeHeaders=true. Priority values: 0=Urgent, 1=Important, 3=Medium, 5=Low, 9=unset.

Input Schema

TableJSON 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.
`If-Match`	Yes	ETag value.
`plannerTaskId`	Yes	Value for the 'plannerTaskId' path segment. Pass it under the name 'plannerTaskId', not as 'id'. Use the 'id' field of the planner task object as returned by Microsoft Graph.
`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. Dates show when Glama detected each change.

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"
```

Changed11 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"

changedInput schema / properties / plannerTaskId / description

Previous value: -"Path parameter: plannerTaskId"New value: +"Value for the 'plannerTaskId' path segment. Pass it under the name 'plannerTaskId', not as 'id'. Use the 'id' field of the planner task object as returned by Microsoft Graph."

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

A4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true. The description adds valuable behavioral context: the If-Match header requirement and the 412 error condition, which is a critical behavioral trait not captured by annotations. It also explains the priority value mapping. The description doesn't contradict annotations. It adds meaningful behavioral disclosure beyond what annotations provide, though it could mention that this is a PATCH operation that only updates specified fields.

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?

The description is concise and front-loaded with the core purpose. The critical If-Match tip is prominently placed with a 💡 emoji and CRITICAL label. The priority values are listed compactly. The description is efficient with no wasted words, though the emoji and formatting could be seen as slightly informal for a tool description. Overall, it's well-structured and earns its place.

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 destructiveHint=true and no output schema, the description covers the critical operational requirements: the If-Match header, the error condition, and the priority mapping. It doesn't explain what the response looks like, but with no output schema, that's less critical. It could mention that only specified properties are updated (PATCH semantics) and that read-only properties should not be included. The description is largely complete for an agent to call this tool correctly, with minor gaps around PATCH semantics and response format.

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 description coverage is 83%, which is high. The description adds value for the If-Match parameter by explaining the ETag requirement and how to obtain it. It also explains priority values in the description, which complements the schema's priority description. The plannerTaskId parameter has a helpful note in the schema about passing it as 'plannerTaskId' not 'id', which is good. The description adds the critical If-Match context that the schema alone doesn't provide, so it compensates well for the 17% gap.

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 a clear verb and resource: 'Update the properties of plannerTask object.' It distinguishes this from sibling tools like create-planner-task and get-planner-task by the verb. However, it doesn't explicitly differentiate from update-planner-task-details, which is a close sibling that also updates planner task properties. The description is clear but could be more specific about which properties are updated (the main task object vs. the details object).

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?

The description provides critical usage guidance: it explains the If-Match header requirement, the 412 error if missing, and how to get the ETag (from get-planner-task with includeHeaders=true). It also explains priority values. However, it doesn't explicitly state when to use this tool vs. update-planner-task-details, which is a significant sibling that also updates planner task properties. The guidance is strong for the If-Match requirement but lacks explicit alternative routing.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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