Skip to main content
Glama
Sign In
Microsoft 365 MCP Server

Microsoft 365 MCP Server

by Softeria
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create-todo-task-list

create-todo-task-list
Destructive

Create a new Microsoft To Do task list to group tasks into named buckets in the To Do app sidebar; use it before adding tasks to that list.

Instructions

Create a new lists object.

šŸ’” TIP: Creates a new Microsoft To Do task list (the named buckets shown in the To Do app sidebar). Body: { displayName: 'My new list' }. Returns the created todoTaskList with its id, displayName, isOwner, isShared, and wellknownListName ('none' for user-created lists). The built-in lists ('Tasks', 'Flagged emails') already exist and cannot be re-created. Pair with create-todo-task to populate it.

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.
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. Changed2 schema fields changedv0.179.1
    • addedInput schema / properties / body / properties / singleValueExtendedProperties
      Added value: +{
+  "description": "The collection of single-value extended properties defined for the task list. Nullable.",
+  "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"
+}
    • addedInput schema / properties / body / properties / tasks / items / 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"
+}
  2. Changed5 schema fields changedv0.176.1
    • removedInput schema / properties / body / properties / tasks / items / 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 / tasks / items / 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 / tasks / items / properties / checklistItems / items / properties / checkedDateTime / description
      Removed value: -"The date and time when the checklistItem was finished."
    • removedInput schema / properties / body / properties / tasks / items / 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 / tasks / items / 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."
  3. Changed29 schema fields changedv0.145.2
    • removedInput schema / $defs
      Removed value: -{
-  "def0": {
-    "additionalProperties": true,
-    "properties": {
-      "id": {
-        "description": "The unique identifier for an entity. Read-only.",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "def1": {
-    "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"
-  },
-  "def2": {
-    "enum": [
-      "sunday",
-      "monday",
-      "tuesday",
-      "wednesday",
-      "thursday",
-      "friday",
-      "saturday"
-    ],
-    "type": "string"
-  }
-}
    • removedInput schema / properties / body / properties / extensions / items / $ref
      Removed value: -"#/$defs/def0"
    • addedInput schema / properties / body / properties / extensions / items / additionalProperties
      Added value: +true
    • addedInput schema / properties / body / properties / extensions / items / properties
      Added value: +{
+  "id": {
+    "description": "The unique identifier for an entity. Read-only.",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / body / properties / extensions / items / type
      Added value: +"object"
    • removedInput schema / properties / body / properties / tasks / items / properties / completedDateTime / $ref
      Removed value: -"#/$defs/def1"
    • addedInput schema / properties / body / properties / tasks / items / properties / completedDateTime / additionalProperties
      Added value: +true
    • addedInput schema / properties / body / properties / tasks / items / 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 / tasks / items / properties / completedDateTime / type
      Added value: +"object"
    • removedInput schema / properties / body / properties / tasks / items / properties / dueDateTime / $ref
      Removed value: -"#/$defs/def1"
    • addedInput schema / properties / body / properties / tasks / items / properties / dueDateTime / additionalProperties
      Added value: +true
    • addedInput schema / properties / body / properties / tasks / items / 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 / tasks / items / properties / dueDateTime / type
      Added value: +"object"
    • removedInput schema / properties / body / properties / tasks / items / properties / extensions / items / $ref
      Removed value: -"#/$defs/def0"
    • addedInput schema / properties / body / properties / tasks / items / properties / extensions / items / additionalProperties
      Added value: +true
    • addedInput schema / properties / body / properties / tasks / items / properties / extensions / items / properties
      Added value: +{
+  "id": {
+    "description": "The unique identifier for an entity. Read-only.",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / body / properties / tasks / items / properties / extensions / items / type
      Added value: +"object"
    • changedInput schema / properties / body / properties / tasks / items / properties / recurrence / properties / pattern / properties / daysOfWeek / items / anyOf
      Previous value: -[
-  {
-    "$ref": "#/$defs/def2"
-  },
-  {
-    "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 / tasks / items / properties / recurrence / properties / pattern / properties / firstDayOfWeek / $ref
      Removed value: -"#/$defs/def2"
    • addedInput schema / properties / body / properties / tasks / items / properties / recurrence / properties / pattern / properties / firstDayOfWeek / enum
      Added value: +[
+  "sunday",
+  "monday",
+  "tuesday",
+  "wednesday",
+  "thursday",
+  "friday",
+  "saturday"
+]
    • addedInput schema / properties / body / properties / tasks / items / properties / recurrence / properties / pattern / properties / firstDayOfWeek / type
      Added value: +"string"
    • removedInput schema / properties / body / properties / tasks / items / properties / reminderDateTime / $ref
      Removed value: -"#/$defs/def1"
    • addedInput schema / properties / body / properties / tasks / items / properties / reminderDateTime / additionalProperties
      Added value: +true
    • addedInput schema / properties / body / properties / tasks / items / 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 / tasks / items / properties / reminderDateTime / type
      Added value: +"object"
    • removedInput schema / properties / body / properties / tasks / items / properties / startDateTime / $ref
      Removed value: -"#/$defs/def1"
    • addedInput schema / properties / body / properties / tasks / items / properties / startDateTime / additionalProperties
      Added value: +true
    • addedInput schema / properties / body / properties / tasks / items / 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 / tasks / items / properties / startDateTime / type
      Added value: +"object"
  4. Addedv0.135.0
  5. Removedv0.134.4
  6. Changed1 schema field changedv0.131.2
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +true
  7. 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"
+}
  8. Addedv0.114.0
  9. Removedv0.112.2
  10. Addedv0.110.0
  11. Removedv0.108.0
  12. Addedv0.105.0

TDQS

A3.8/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 agent knows this is a mutating call. The description adds useful behavior beyond that: the returned fields (id, displayName, isOwner, isShared, wellknownListName) and the constraint that built-in lists cannot be recreated. It omits the confirm-gate behavior for destructive operations and any permission/scope requirements, which matters given destructiveHint=true.

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?

Compact and structured, with the concrete meaning, body example, return shape, and constraint each earning their place. The first sentence 'Create a new lists object' is redundant with the TIP that follows and could be dropped without loss.

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?

There is no output schema, so the description properly covers the return value, and it explains the body shape and the built-in-list limitation. For a create tool with a heavily nested input schema this is nearly sufficient; the missing piece is any mention of the confirmation gate that governs this destructive-hinted operation.

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 schema coverage at 75%, the baseline is 3, but the description usefully clarifies that body is effectively { displayName: 'My new list' } ā€” valuable because the nested schema superficially offers dozens of read-only task fields that should not be sent. It does not address the confirm, includeHeaders, or excludeResponse parameters, though their schema descriptions are self-explanatory.

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?

The TIP sentence states a specific verb and resource: creates a Microsoft To Do task list, described as 'the named buckets shown in the To Do app sidebar,' which is concrete for an agent. It implicitly distinguishes itself from create-todo-task ('Pair with create-todo-task to populate it'). The opening line 'Create a new lists object' is vague and slightly undermines the otherwise sharp statement.

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 clear when-to-use context (making a new task list) and an explicit when-not: the built-in lists 'Tasks' and 'Flagged emails' already exist and cannot be re-created. It also names the follow-up tool, create-todo-task. It does not mention list-todo-task-lists as a way to check existing lists first, so one alternative is left implicit.

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