Microsoft 365 MCP Server

update-todo-task

update-todo-task

Destructive

Update a Microsoft To Do task's properties to mark it complete or reopen it, rename it, adjust due dates, reminders, importance, or notes.

Instructions

Update the properties of a todoTask object.

💡 TIP: Updates a Microsoft To Do task. Use this to mark a to-do item complete or done (body: { status: "completed" }), reopen it (status: "notStarted"), rename it (title), or change its due date (dueDateTime), reminder (reminderDateTime), importance, or notes (body). Requires todoTaskListId from list-todo-task-lists and todoTaskId from list-todo-tasks. Steps (checklistItems) can't be changed here: Graph rejects checklistItems in a PATCH on the task with 400. Use create-todo-checklist-item, update-todo-checklist-item, or delete-todo-checklist-item instead.

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.
`todoTaskId`	Yes	Value for the 'todoTaskId' path segment. Pass it under the name 'todoTaskId', not as 'id'. Use the 'id' field of the todo task object as returned by Microsoft Graph.
`includeHeaders`	No	Include response headers (including ETag) in the response metadata
`todoTaskListId`	Yes	Value for the 'todoTaskListId' path segment. Pass it under the name 'todoTaskListId', not as 'id'. Use the 'id' field of the todo task list object as returned by Microsoft Graph.
`excludeResponse`	No	Exclude the full response body and only return success or failure indication

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.179.1Nov 5, 2026

addedInput schema / properties / body / properties / singleValueExtendedProperties

Added value: +{
+  "description": "A collection of custom fields linked to the task.",
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "id": {
+        "description": "The unique identifier for an entity. Read-only.",
+        "type": "string"
+      },
+      "value": {
+        "description": "The value of the property.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

Changed5 schema fields changedv0.176.1Oct 29, 2026

removed

Input schema / properties / body / properties / attachmentSessions / items / properties / expirationDateTime / description

Removed value: -"The date and time in UTC when the upload session will expire. The complete file must be uploaded before this expiration time is reached."

removedInput schema / properties / body / properties / attachments / items / properties / lastModifiedDateTime / description

Removed value: -"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 / checklistItems / items / properties / checkedDateTime / description
```
Removed value: -"The date and time when the checklistItem was finished."
```

removedInput schema / properties / body / properties / recurrence / properties / range / properties / endDate / description

Removed value: -"The date to stop applying the recurrence pattern. Depending on the recurrence pattern of the event, the last occurrence of the meeting may not be this date. Required if type is endDate."

removedInput schema / properties / body / properties / recurrence / properties / range / properties / startDate / description

Removed value: -"The date to start applying the recurrence pattern. The first occurrence of the meeting may be this date or later, depending on the recurrence pattern of the event. Must be the same value as the start property of the recurring event. Required."

Changed21 schema fields changedv0.145.2Aug 22, 2026

removedInput schema / $defs

Removed value: -{
-  "def0": {
-    "additionalProperties": true,
-    "properties": {
-      "dateTime": {
-        "description": "A single point of time in a combined date and time representation ({date}T{time}; for example, 2017-08-29T04:00:00.0000000).",
-        "type": "string"
-      },
-      "timeZone": {
-        "description": "Represents a time zone, for example, 'Pacific Standard Time'. See below for more possible values.",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  },
-  "def1": {
-    "enum": [
-      "sunday",
-      "monday",
-      "tuesday",
-      "wednesday",
-      "thursday",
-      "friday",
-      "saturday"
-    ],
-    "type": "string"
-  }
-}

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

addedInput schema / properties / body / properties / completedDateTime / properties

Added value: +{
+  "dateTime": {
+    "description": "A single point of time in a combined date and time representation ({date}T{time}; for example, 2017-08-29T04:00:00.0000000).",
+    "type": "string"
+  },
+  "timeZone": {
+    "description": "Represents a time zone, for example, 'Pacific Standard Time'. See below for more possible values.",
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}

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

addedInput schema / properties / body / properties / dueDateTime / properties

Added value: +{
+  "dateTime": {
+    "description": "A single point of time in a combined date and time representation ({date}T{time}; for example, 2017-08-29T04:00:00.0000000).",
+    "type": "string"
+  },
+  "timeZone": {
+    "description": "Represents a time zone, for example, 'Pacific Standard Time'. See below for more possible values.",
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}

addedInput schema / properties / body / properties / dueDateTime / type
```
Added value: +"object"
```

changed

Input schema / properties / body / properties / recurrence / properties / pattern / properties / daysOfWeek / items / anyOf

Previous value: -[
-  {
-    "$ref": "#/$defs/def1"
-  },
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  }
-]New value: +[
+  {
+    "enum": [
+      "sunday",
+      "monday",
+      "tuesday",
+      "wednesday",
+      "thursday",
+      "friday",
+      "saturday"
+    ],
+    "type": "string"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {},
+    "type": "object"
+  }
+]

removedInput schema / properties / body / properties / recurrence / properties / pattern / properties / firstDayOfWeek / $ref
```
Removed value: -"#/$defs/def1"
```
addedInput schema / properties / body / properties / recurrence / properties / pattern / properties / firstDayOfWeek / enum
```
Added value: +[
+  "sunday",
+  "monday",
+  "tuesday",
+  "wednesday",
+  "thursday",
+  "friday",
+  "saturday"
+]
```
addedInput schema / properties / body / properties / recurrence / properties / pattern / properties / firstDayOfWeek / type
```
Added value: +"string"
```
removedInput schema / properties / body / properties / reminderDateTime / $ref
```
Removed value: -"#/$defs/def0"
```
addedInput schema / properties / body / properties / reminderDateTime / additionalProperties
```
Added value: +true
```

addedInput schema / properties / body / properties / reminderDateTime / properties

Added value: +{
+  "dateTime": {
+    "description": "A single point of time in a combined date and time representation ({date}T{time}; for example, 2017-08-29T04:00:00.0000000).",
+    "type": "string"
+  },
+  "timeZone": {
+    "description": "Represents a time zone, for example, 'Pacific Standard Time'. See below for more possible values.",
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}

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

addedInput schema / properties / body / properties / startDateTime / properties

Added value: +{
+  "dateTime": {
+    "description": "A single point of time in a combined date and time representation ({date}T{time}; for example, 2017-08-29T04:00:00.0000000).",
+    "type": "string"
+  },
+  "timeZone": {
+    "description": "Represents a time zone, for example, 'Pacific Standard Time'. See below for more possible values.",
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}

addedInput schema / properties / body / properties / startDateTime / type
```
Added value: +"object"
```

Changed12 schema fields changedv0.134.4Jul 28, 2026

addedInput schema / $defs

Added value: +{
+  "def0": {
+    "additionalProperties": true,
+    "properties": {
+      "dateTime": {
+        "description": "A single point of time in a combined date and time representation ({date}T{time}; for example, 2017-08-29T04:00:00.0000000).",
+        "type": "string"
+      },
+      "timeZone": {
+        "description": "Represents a time zone, for example, 'Pacific Standard Time'. See below for more possible values.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "def1": {
+    "enum": [
+      "sunday",
+      "monday",
+      "tuesday",
+      "wednesday",
+      "thursday",
+      "friday",
+      "saturday"
+    ],
+    "type": "string"
+  }
+}

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

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

Removed value: -{
-  "dateTime": {
-    "description": "A single point of time in a combined date and time representation ({date}T{time}; for example, 2017-08-29T04:00:00.0000000).",
-    "type": "string"
-  },
-  "timeZone": {
-    "description": "Represents a time zone, for example, 'Pacific Standard Time'. See below for more possible values.",
-    "type": [
-      "string",
-      "null"
-    ]
-  }
-}

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

changedInput schema / properties / body / properties / dueDateTime / $ref

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

changed

Input schema / properties / body / properties / recurrence / properties / pattern / properties / daysOfWeek / items / anyOf

Previous value: -[
-  {
-    "enum": [
-      "sunday",
-      "monday",
-      "tuesday",
-      "wednesday",
-      "thursday",
-      "friday",
-      "saturday"
-    ],
-    "type": "string"
-  },
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  }
-]New value: +[
+  {
+    "$ref": "#/$defs/def1"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {},
+    "type": "object"
+  }
+]

changedInput schema / properties / body / properties / recurrence / properties / pattern / properties / firstDayOfWeek / $ref

Previous value: -"#/properties/body/properties/recurrence/properties/pattern/properties/daysOfWeek/items/anyOf/0"New value: +"#/$defs/def1"

changedInput schema / properties / body / properties / reminderDateTime / $ref

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

changedInput schema / properties / body / properties / startDateTime / $ref

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

changedInput schema / properties / todoTaskId / description

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

changedInput schema / properties / todoTaskListId / description

Previous value: -"Path parameter: todoTaskListId"New value: +"Value for the 'todoTaskListId' path segment. Pass it under the name 'todoTaskListId', not as 'id'. Use the 'id' field of the todo task list 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
Changed12 schema fields changedv0.96.0May 4, 2026
- changedInput schema / properties / body / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / attachmentSessions / items / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / attachments / items / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / body / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / checklistItems / items / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / completedDateTime / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / extensions / items / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / linkedResources / items / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / recurrence / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / recurrence / properties / pattern / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedInput schema / properties / body / properties / recurrence / properties / pattern / properties / daysOfWeek / items / anyOf
```
Previous value: -[
-  {
-    "enum": [
-      "sunday",
-      "monday",
-      "tuesday",
-      "wednesday",
-      "thursday",
-      "friday",
-      "saturday"
-    ],
-    "type": "string"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {},
-    "type": "object"
-  }
-]New value: +[
+  {
+    "enum": [
+      "sunday",
+      "monday",
+      "tuesday",
+      "wednesday",
+      "thursday",
+      "friday",
+      "saturday"
+    ],
+    "type": "string"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {},
+    "type": "object"
+  }
+]
```
- changedInput schema / properties / body / properties / recurrence / properties / range / additionalProperties
```
Previous value: -falseNew value: +true
```
First observedv0.31.0Jan 27, 2026

TDQS

A4.3/5.0

Behavior4/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 description doesn't need to establish that this mutates state. It adds genuine non-schema knowledge: Graph rejects checklistItems in a PATCH with a 400, and IDs form a dependency chain off the list tools. The gap is that it never mentions the confirm gate or what happens to fields not supplied, though the confirm parameter's own schema description covers the gate.

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?

Front-loaded with the purpose, then a TIP block of concrete operations, prerequisites, and the exclusion — a sensible ordering. Minor waste in the heading restating the title and the redundant parenthetical "(status: \"notStarted\")" after already saying "reopen it", but nothing is padding.

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 a large nested body object, six parameters, and no output schema, the description covers the common field set, the ID prerequisites, and the one trap (checklistItems) that would otherwise produce a 400. It stops short of noting the destructive/confirm behavior or the broader writable fields (recurrence, categories, startDateTime), which the deeply described schema partly compensates for.

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?

Schema description coverage is 83%, so the baseline is 3 and the schema already carries most of the load. The description does add real meaning on top—mapping the friendly intent ("notes", "rename") onto the actual body.title, body.body, and status fields, and warning that checklistItems is present in the schema but will fail—which is more than a bare restatement, but it doesn't cover the confirm/includeHeaders/excludeResponse control parameters.

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?

States a specific verb and resource ("Update the properties of a todoTask object") and immediately grounds it in the product ("Updates a Microsoft To Do task"). It then enumerates the concrete mutations available (status, title, dueDateTime, reminderDateTime, importance, notes), so an agent can distinguish it from update-todo-task-list, update-planner-task, or update-todo-checklist-item without opening any schema.

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?

Explicit when-to-use guidance with literal payloads ("mark complete" → body: { status: "completed" }, "reopen" → notStarted), explicit prerequisites (todoTaskListId from list-todo-task-lists, todoTaskId from list-todo-tasks), and an explicit exclusion naming three alternative siblings for checklist items. This is the when/when-not/alternatives pattern in full.

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

Deploy Server

update-todo-task

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools