Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

create-todo-task-list

create-todo-task-list
Destructive

Create a named Microsoft To Do task list to organize tasks into buckets. Returns the new list's details so you can add tasks to it.

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

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

  1. 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"
  2. Addedv0.135.0
  3. Removedv0.134.4
  4. Changed1 schema field changedv0.131.2
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +true
  5. 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"
+}
  6. Addedv0.114.0
  7. Removedv0.112.2
  8. Addedv0.110.0
  9. Removedv0.108.0
  10. Addedv0.105.0

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already flag this as a non-read-only, destructive-capable write operation, and the description adds useful behavioral details: the body shape is { displayName: 'My new list' }, the returned fields include id/displayName/isOwner/isShared/wellknownListName, and user-created lists get wellknownListName 'none'. No contradictions with annotations.

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 description is compact and front-loaded with the most useful information. The only mild redundancy is the opening 'Create a new lists object', which echoes the title and is less precise than the tip that follows, but overall every sentence earns its place.

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?

Even without an output schema, the description states what the tool returns and what input is required, which makes it largely complete for a simple creation tool. It does not explain the confirm parameter behavior, but that is fully documented in the input schema itself.

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 coverage is 75%, so much of the parameter meaning is already documented. The description still adds value by explicitly providing the required body example, { displayName: 'My new list' }, and explaining what the returned wellknownListName will be, which is more practical than the raw 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 ā€” 'Creates a new Microsoft To Do task list' ā€” and explains what that means via the app-sidebar analogy. It differentiates from create-todo-task by explicitly saying to pair with that tool to populate the list, so an agent can tell them apart.

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?

The description gives actionable usage context: built-in lists like 'Tasks' and 'Flagged emails' already exist and cannot be re-created, and the tool should be paired with create-todo-task to add tasks. It does not explicitly discuss when to use update-todo-task-list instead, but the create-vs-update distinction is clear enough.

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

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