Microsoft 365 MCP Server

list-todo-task-lists

list-todo-task-lists

Read-only

Lists all Microsoft To Do task lists and returns their IDs, which are required for creating, updating, or reading tasks in those lists.

Instructions

Get a list of the todoTaskList objects and their properties.

💡 TIP: Lists all To Do task lists. Returns todoTaskList-id needed for all task operations. The default list is typically called 'Tasks'. NOTE: $select is NOT supported by this endpoint — do not pass select parameter, Graph returns 400.

Input Schema

TableJSON Schema

Name	Required	Description
`top`	No	Page size (Graph $top). Start small (e.g. 5–15) so responses fit the model context; raise only if needed. Use $select to return fewer fields per item. For more rows, use @odata.nextLink from the response instead of a very large $top.
`skip`	No	Items to skip for pagination. Not supported with $search.
`count`	No	Set true to enable advanced query mode (ConsistencyLevel: eventual). Required for complex $filter on flag/flagStatus or contains().
`expand`	No	Navigation properties to inline, e.g. attachments on a message or event. Only navigation properties can be expanded: expanding a non-navigation property such as a message body fails with "Parsing OData Select and Expand failed", and an unsupported value may be ignored rather than reported. Request ordinary fields with $select instead.
`filter`	No	OData filter expression. Add $count=true for advanced filters (flag/flagStatus, contains()). Cannot combine with $search.
`search`	No	KQL search query in one pair of double quotes; directory (users/groups) instead quotes each clause with no outer pair. Cannot combine with $filter.
`select`	No	Comma-separated fields to return, e.g. id,subject,from,receivedDateTime
`orderby`	No	Sort expression, e.g. receivedDateTime desc
`skiptoken`	No	Next page: the @odata.nextLink from the previous response. Keep the other arguments the same.
`fetchAllPages`	No	Follow @odata.nextLink and merge up to 100 pages into one response. Can return enormous payloads—only when the user explicitly needs a full export. Prefer a small $top first, then paginate or narrow with $filter/$search.
`includeHeaders`	No	Include response headers (including ETag) in the response metadata
`excludeResponse`	No	Exclude the full response body and only return success or failure indication

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.154.2Sep 17, 2026

addedInput schema / properties / expand / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

removedInput schema / properties / expand / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / expand / type
```
Removed value: -"array"
```

addedInput schema / properties / orderby / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

removedInput schema / properties / orderby / type
```
Removed value: -"string"
```

addedInput schema / properties / select / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

removedInput schema / properties / select / type
```
Removed value: -"string"
```
addedInput schema / properties / skip / minimum
```
Added value: +0
```

changedInput schema / properties / skip / type

Previous value: -"number"New value: +"integer"

addedInput schema / properties / top / minimum
```
Added value: +0
```

changedInput schema / properties / top / type

Previous value: -"number"New value: +"integer"

Changed1 schema field changedv0.154.0Sep 12, 2026

changedInput schema / properties / skiptoken / description

Previous value: -"Opaque cursor for the next page, taken from the previous response. Copy the $skiptoken value out of @odata.nextLink (or paste the whole nextLink URL — the token is extracted from it) and resend it with the SAME $filter/$select/$expand/$top as the first call. Use this to walk pages one at a time instead of fetchAllPages. Omit it for the first page."New value: +"Next page: the @odata.nextLink from the previous response. Keep the other arguments the same."

Changed2 schema fields changedv0.153.0Sep 12, 2026

changedInput schema / properties / search / description

Previous value: -"KQL search query — wrap value in double quotes. Cannot combine with $filter."New value: +"KQL search query in one pair of double quotes; directory (users/groups) instead quotes each clause with no outer pair. Cannot combine with $filter."

addedInput schema / properties / skiptoken

Added value: +{
+  "description": "Opaque cursor for the next page, taken from the previous response. Copy the $skiptoken value out of @odata.nextLink (or paste the whole nextLink URL — the token is extracted from it) and resend it with the SAME $filter/$select/$expand/$top as the first call. Use this to walk pages one at a time instead of fetchAllPages. Omit it for the first page.",
+  "type": "string"
+}

Changed1 schema field changedv0.134.4Jul 28, 2026

changedInput schema / properties / expand / description

Previous value: -"Expand related entities"New value: +"Navigation properties to inline, e.g. attachments on a message or event. Only navigation properties can be expanded: expanding a non-navigation property such as a message body fails with \"Parsing OData Select and Expand failed\", and an unsupported value may be ignored rather than reported. Request ordinary fields with $select instead."

Changed1 schema field changedv0.131.2Jul 18, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
Addedv0.114.0May 28, 2026
Removedv0.112.2May 22, 2026
Addedv0.110.0May 18, 2026
Removedv0.108.0May 15, 2026

Changed16 schema fields changedv0.96.0May 4, 2026

changedInput schema / properties / count / description

Previous value: -"Include count of items"New value: +"Set true to enable advanced query mode (ConsistencyLevel: eventual). Required for complex $filter on flag/flagStatus or contains()."

changedInput schema / properties / fetchAllPages / description

Previous value: -"Automatically fetch all pages of results"New value: +"Follow @odata.nextLink and merge up to 100 pages into one response. Can return enormous payloads—only when the user explicitly needs a full export. Prefer a small $top first, then paginate or narrow with $filter/$search."

changedInput schema / properties / filter / description

Previous value: -"Filter items by property values"New value: +"OData filter expression. Add $count=true for advanced filters (flag/flagStatus, contains()). Cannot combine with $search."

changedInput schema / properties / orderby / description

Previous value: -"Order items by property values"New value: +"Sort expression, e.g. receivedDateTime desc"

removedInput schema / properties / orderby / items
```
Removed value: -{
-  "type": "string"
-}
```
changedInput schema / properties / orderby / type
```
Previous value: -"array"New value: +"string"
```

changedInput schema / properties / search / description

Previous value: -"Search items by search phrases"New value: +"KQL search query — wrap value in double quotes. Cannot combine with $filter."

changedInput schema / properties / select / description

Previous value: -"Select properties to be returned"New value: +"Comma-separated fields to return, e.g. id,subject,from,receivedDateTime"

removedInput schema / properties / select / items
```
Removed value: -{
-  "type": "string"
-}
```

changedInput schema / properties / select / type

Previous value: -"array"New value: +"string"

changedInput schema / properties / skip / description

Previous value: -"Skip the first n items"New value: +"Items to skip for pagination. Not supported with $search."

removedInput schema / properties / skip / minimum
```
Removed value: -0
```

changedInput schema / properties / skip / type

Previous value: -"integer"New value: +"number"

changedInput schema / properties / top / description

Previous value: -"Show only the first n items"New value: +"Page size (Graph $top). Start small (e.g. 5–15) so responses fit the model context; raise only if needed. Use $select to return fewer fields per item. For more rows, use @odata.nextLink from the response instead of a very large $top."

removedInput schema / properties / top / minimum
```
Removed value: -0
```

changedInput schema / properties / top / type

Previous value: -"integer"New value: +"number"

First observedv0.31.0Jan 27, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Although annotations already mark the tool as read-only and non-destructive, the description adds a valuable behavioral warning: $select is not supported and passing it causes a Graph 400. It also notes the default list is typically called 'Tasks', which is useful contextual behavior.

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 well-structured: a clear purpose sentence, a scannable tip, and a critical note. Every sentence contributes useful information without repetition.

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 simple read-only listing operation, the description provides enough context: what it returns, the common default list, and the key $select caveat. The input schema covers pagination and filtering details, so the description does not need to repeat them.

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 descriptions cover 100% of parameters, so the baseline is 3. The description adds important parameter-level guidance by explicitly warning that the select parameter must not be passed despite the schema documenting it generically. This is a meaningful correction beyond 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 starts with a specific verb and resource: 'Get a list of the todoTaskList objects and their properties.' It also clarifies it lists all To Do task lists, which distinguishes it from related tools like list-todo-tasks.

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 clearly states this endpoint returns the todoTaskList-id needed for all task operations, giving the agent context for when to call it before task-related operations. It does not explicitly name sibling alternatives or exclusions, but the usage context is clear.

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

Deploy Server

list-todo-task-lists

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools