Microsoft 365 MCP Server

create-todo-task

create-todo-task

Destructive

Creates a new task in a specified Microsoft To Do list, with optional due date, reminder, importance, notes, recurrence, categories, and checklist steps.

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

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.

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

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

A3.9/5.0

Behavior3/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 write nature is covered. The description adds genuinely useful behavior — that checklist steps can be created inline in one call and that isChecked is optional — but says nothing about the confirm gate (only documented in the schema), the auth requirement, or what the call returns. Adequate rather than rich, given the annotation coverage.

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 core statement is front-loaded and the rest is dense, example-driven, and useful. The only waste is the TIP line opening with "Creates a new task in a Microsoft To Do list", which restates the first sentence before adding the checklistItems detail.

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 tool with a very large nested payload, no output schema, and multiple look-alike siblings, the description covers the required inputs, the highest-value optional fields, the id dependency, and where to go for later mutations. Missing pieces — the return shape and the destructive/confirm behavior — are partly carried by the schema, so the gap is small.

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 80%, so the baseline is 3. The description does add some framing beyond the schema by naming the practical payload shape ({ title: ... } plus optional dueDateTime, reminderDateTime, importance, recurrence, categories, checklistItems) and flagging isChecked as optional. However, calling "body" the notes field while the top-level required parameter is also named body is mildly ambiguous, and the remaining parameters (confirm, includeHeaders, excludeResponse) are left entirely to 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 gives a specific verb and resource ("Create a new task object in a specified todoTaskList") and immediately positions it against siblings: it says steps are created inline via checklistItems, and that post-creation step edits belong to the *-todo-checklist-item tools. An agent can distinguish this from update-todo-task and create-todo-checklist-item without consulting either 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?

It states the prerequisite ("Requires todoTaskListId from list-todo-task-lists") and an explicit alternative for the after-creation case. It does not cover when to prefer this over create-planner-task or how to obtain a list id if none exists, so it is strong but not exhaustive.

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