Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

update-todo-task-list

update-todo-task-list
Destructive

Rename a Microsoft To Do task list by setting a new displayName. Works for custom lists; built-in lists cannot be renamed.

Instructions

Update the properties of a todoTaskList object.

šŸ’” TIP: Renames a Microsoft To Do task list. Body: { displayName: 'New name' }. Only displayName is writable. Built-in lists (Flagged emails, the default Tasks list) cannot be renamed ā€” the API returns an error. Get list ids via list-todo-task-lists.

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
todoTaskListIdYesValue 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.
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.6/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description doesn't need to restate that. The description adds valuable behavioral context: the API returns an error for built-in lists, and only displayName is writable. It also mentions the confirm gate in the schema, but the description itself doesn't mention the confirm parameter. However, the description's tip about the error case and the writable property goes beyond annotations, so a 4 is appropriate.

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 front-loaded: the first sentence states the purpose, and the tip immediately provides the most critical usage detail (rename, body format, writable property, error case, and how to get IDs). Every sentence earns its place; no fluff.

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?

Given the tool's complexity (5 params, nested body object, no output schema), the description covers the essential points: what to update, the only writable field, the error case, and how to obtain the ID. It doesn't mention the confirm parameter or the includeHeaders/excludeResponse options, but those are self-explanatory from the schema. The description is complete enough for an agent to call this correctly.

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 description coverage is 80%, and the description adds key semantics: it clarifies that the body should contain { displayName: 'New name' } and that only displayName is writable. It also clarifies the todoTaskListId parameter by saying to pass it under that name and use the 'id' field from list-todo-task-lists. This adds meaning beyond the schema's generic descriptions.

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 tool updates a todoTaskList object, and the tip explicitly says it renames a Microsoft To Do task list. It specifies the writable property (displayName) and distinguishes it from related operations like list-todo-task-lists. The verb 'update' plus the resource 'todoTaskList' is specific and unambiguous.

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 provides explicit guidance: it says only displayName is writable, and it warns that built-in lists (Flagged emails, default Tasks list) cannot be renamed and will return an error. It also tells the agent to get list ids via list-todo-task-lists, which is a clear pointer to the prerequisite step. This is strong usage guidance.

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