Skip to main content
Glama
Sign In
Microsoft 365 MCP Server

Microsoft 365 MCP Server

by Softeria
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list-todo-checklist-items

list-todo-checklist-items
Read-only

Retrieve checklist items for a Microsoft To Do task using its task list ID and task ID, returning each item's name, checked status, and timestamps.

Instructions

Get the checklistItem resources associated to a todoTask from the checklistItems navigation property.

đź’ˇ TIP: Lists the steps (checklist items) of a To Do task. Each item has id, displayName, isChecked, checkedDateTime, and createdDateTime. Requires todoTaskListId from list-todo-task-lists and todoTaskId from list-todo-tasks.

Input Schema

NameRequiredDescriptionDefault
todoTaskIdYesValue for the 'todoTaskId' path segment. Pass it under the name 'todoTaskId', not as 'id'. Use the 'id' field of the todo task object as returned by Microsoft Graph.
fetchAllPagesNoFollow @odata.nextLink and merge up to 100 pages into one response. Can return enormous payloads—only when the user explicitly needs a full export.
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.

  1. Changed10 schema fields changedv0.170.1
    • removedInput schema / properties / count
      Removed value: -{
-  "description": "Set true to enable advanced query mode (ConsistencyLevel: eventual). Required for complex $filter on flag/flagStatus or contains(). The response then includes @odata.count, the total for the filtered collection, which can exceed the items returned when fetchAllPages hits its page/item cap.",
-  "type": "boolean"
-}
    • removedInput schema / properties / expand
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    }
-  ],
-  "description": "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\". Request ordinary fields with $select instead. Some APIs accept only one relationship per request, so prefer a single value. Some relationships support nested selection, e.g. children($select=id,name)."
-}
    • changedInput schema / properties / fetchAllPages / description
      Previous 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."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."
    • removedInput schema / properties / filter
      Removed value: -{
-  "description": "OData filter expression. Add $count=true for advanced filters (flag/flagStatus, contains()). Cannot combine with $search.",
-  "type": "string"
-}
    • removedInput schema / properties / orderby
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    }
-  ],
-  "description": "Sort expression, e.g. receivedDateTime desc"
-}
    • removedInput schema / properties / search
      Removed value: -{
-  "description": "KQL search query in one pair of double quotes; directory (users/groups) instead quotes each clause with no outer pair. Cannot combine with $filter.",
-  "type": "string"
-}
    • removedInput schema / properties / select
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    }
-  ],
-  "description": "Comma-separated fields to return, e.g. id,subject,from,receivedDateTime"
-}
    • removedInput schema / properties / skip
      Removed value: -{
-  "description": "Items to skip for pagination. Not supported with $search.",
-  "minimum": 0,
-  "type": "integer"
-}
    • removedInput schema / properties / skiptoken
      Removed value: -{
-  "description": "Next page: the @odata.nextLink from the previous response. Keep the other arguments the same.",
-  "type": "string"
-}
    • removedInput schema / properties / top
      Removed value: -{
-  "description": "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.",
-  "minimum": 0,
-  "type": "integer"
-}
  2. Addedv0.166.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by enumerating the returned fields (id, displayName, isChecked, checkedDateTime, createdDateTime) and the navigation property source, which matters since there is no output schema.

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?

Front-loads the plain-language TIP before the OData-style 'navigation property' phrasing, and every clause carries information (resource, returned fields, required IDs). Slightly redundant between the formal sentence and the TIP, but no wasted content.

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?

With no output schema, the description correctly compensates by listing the returned fields, and it covers input provenance for both required IDs. It could mention pagination behavior, but the fetchAllPages caveat already lives in the schema, so the definition is substantively complete.

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 100%, so the baseline is 3, but the description goes further by explaining where the two required IDs come from (list-todo-task-lists and list-todo-tasks), which is workflow semantics the schema cannot convey. The three optional pagination/output-shaping params remain only in 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?

States a specific verb (Get/Lists) and resource (checklistItem resources / the steps of a To Do task) and identifies the source navigation property. The plain-language TIP makes it trivially distinguishable from siblings like list-todo-tasks or get-todo-task.

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?

Explicitly states the prerequisites: it requires todoTaskListId from list-todo-task-lists and todoTaskId from list-todo-tasks, which tells the agent when the tool is callable and how to obtain inputs. It stops short of naming an alternative tool to prefer under other conditions, but the workflow 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

Other Tools