Microsoft 365 MCP Server

update-todo-task

update-todo-task

Destructive

Modify a Microsoft To Do task to change its status, title, due date, reminder, importance, or notes. Use this to mark tasks completed, reopen them, or adjust scheduling details.

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.

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.
`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. Dates show when Glama detected each change.

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.4/5.0

Behavior3/5

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

The description states that it updates the task, which implies modification, but does not explicitly warn about destructive implications or mention permissions or side effects. The annotations already indicate destructiveHint and readOnlyHint false, so the description adds minimal behavioral context beyond what is implied by 'update'.

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 compact and well-organized: a clear opening sentence followed by a TIP with examples and prerequisites. No redundancy or unnecessary details.

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?

The description covers the essential information needed to invoke the tool: what it does, common use cases, and required parameter sourcing. It does not mention the response format or error cases, but given that there is no output schema and the operation is straightforward, it is reasonably complete.

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 descriptions cover most parameters (83% coverage), and the tool description reinforces the purpose of the body parameter (e.g., status, title, dueDateTime) and clarifies the source of the required IDs. It adds practical guidance on how to use parameters, going slightly beyond the schema.

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?

The description clearly states the action ('Update the properties of a todoTask object') and provides concrete examples of updates (mark complete, rename, change due date, etc.). It unambiguously identifies the resource being modified.

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?

The description includes explicit 'Use this to' guidance with specific scenarios, and mentions the required IDs (todoTaskListId and todoTaskId) that must be sourced from list operations. It also shows example usage for common updates, making it highly actionable.

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