Skip to main content
Glama
Sign In
Microsoft 365 MCP Server

Microsoft 365 MCP Server

by Softeria
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update-planner-task

update-planner-task
Destructive

Update Microsoft Planner task details, assignments, priority, dates, or completion status; include the task's ETag to avoid version conflicts.

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 is 0-10 (lower = higher priority); Planner's own UI presets are 1=Urgent, 3=Important, 5=Medium, 9=Low.

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.
If-MatchYesETag value.
plannerTaskIdYesValue 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.
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.

  1. Changed9 schema fields changedv0.176.1
    • 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"
  2. Changed15 schema fields changedv0.145.2
    • 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"
  3. Changed11 schema fields changedv0.134.4
    • 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."
  4. Changed1 schema field changedv0.131.2
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +true
  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. Changed10 schema fields changedv0.96.0
    • 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
  11. First observedv0.31.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag this as a destructive, non-read-only, open-world mutation, so the bar is lower, and the description still adds substantive behavior: the mandatory ETag/If-Match contract and the exact 412 failure mode with the recovery path. It does not describe what state is replaced/lost on a partial update or the confirmation gate, but the critical failure behavior is disclosed.

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?

Short and front-loaded, with the hard requirement stated first and the ETag recovery path immediately after. The doubled 'šŸ’” TIP: CRITICAL:' prefix is redundant markup, and the priority-preset sentence is partly duplicated by the schema, but no sentence is wasted.

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 6-parameter destructive mutation with nested body objects and no output schema, the description covers the highest-risk detail an agent must get right (ETag/If-Match) and points at the tool that supplies it. Remaining gaps ā€” what a partial body update does to unspecified fields, and the confirm gate for destructive ops ā€” are modest but present.

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 83%, so the baseline is 3; the description earns an extra point by explaining that If-Match must carry the task's @odata.etag and where to obtain it ā€” the schema only says 'ETag value.' The priority explanation (0-10, lower = higher priority, UI presets 1/3/5/9) largely repeats the already-detailed schema description for that field, and no guidance is given for includeHeaders/excludeResponse or the confirm gate.

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?

States a specific verb and resource ('Update the properties of plannerTask object'), which is enough to distinguish it from create-planner-task or get-planner-task. However, it never differentiates itself from the very similar sibling update-planner-task-details, which edits the nested details/checklist/references object rather than the task itself ā€” an agent could easily pick the wrong one.

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?

Gives a concrete operational precondition chain: the call needs an If-Match header sourced from get-planner-task with includeHeaders=true, otherwise it fails with 412. That is real 'how to use this correctly' guidance. It stops short of naming alternatives or exclusions (e.g. when to route to update-planner-task-details instead), so it does not reach a 5.

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