Microsoft 365 MCP Server

create-todo-task

create-todo-task

Destructive

Create a new task object in a specified todoTaskList.

Instructions

Create a new task object in a specified todoTaskList.

💡 TIP: Creates a new task in a Microsoft To Do list. Body: { title: "..." }; optional dueDateTime, reminderDateTime, importance, body (notes), recurrence, categories, and checklistItems: [{ displayName: "...", isChecked: false }] to create the task's steps inline (isChecked is optional). Requires todoTaskListId from list-todo-task-lists. To change steps after the task exists, use the *-todo-checklist-item tools.

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

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

Changed11 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 / 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.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, so the safety profile is covered. The description only adds that checklistItems can be created inline and that steps are edited later via other tools - useful but not rich behavioral context (no failure modes, rate limits, or what the mutation returns).

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 verb+resource followed by a compact tip. Some duplication between the opening sentence and the 'Creates a new task in a Microsoft To Do list' tip line, but no filler.

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 create tool with nested objects and no output schema, the description covers field usage, ID provenance, and step-editing routing. The confirm gate and includeHeaders/excludeResponse flags are left to the schema, which is acceptable.

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?

With 80% schema coverage the baseline is 3, but the description meaningfully adds per-field usage: the Body shape { title: "..." }, the optional fields (dueDateTime, reminderDateTime, importance, body notes, recurrence, categories), and the checklistItems sub-structure including that isChecked is optional.

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 ('Create a new task object in a specified todoTaskList') and pins the platform ('Microsoft To Do list'). An agent can distinguish it from list-todo-tasks, update-todo-task, and create-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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the prerequisite source for todoTaskListId (list-todo-task-lists) and explicitly routes post-creation step edits to the '*-todo-checklist-item tools'. Clear context, though it does not distinguish this from sibling creators like create-planner-task.

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

Deploy Server

create-todo-task

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools