Skip to main content
Glama

graph_list_todo_tasks

List tasks in a Microsoft To Do list, with paging, OData filters, and optional completed-task inclusion.

Instructions

List tasks in a Microsoft To Do list.

Args: list_id: The task list ID (from graph_list_todo_lists). top: Maximum number of tasks to return (default 25, maximum 50). filter_query: Optional OData filter (e.g. "status eq 'completed'"). Replaces the default incomplete-only filter. include_completed: Whether to include completed tasks (default false). When false and no filter_query is given, only incomplete tasks are returned. skip: Number of items to skip before returning results (default 0). Graph returns at most 50 per call, so page by raising skip in steps of top. next_link: Opaque nextLink URL from a previous call, used to fetch the next page. Overrides the other paging arguments when supplied. include_next_link: Whether to wrap the result as {items, next_link} so paging can continue (default false, which returns a bare list).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "list_id": "<list_id>"
    },
    "name": "graph_list_todo_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
skipNo
list_idYes
next_linkNo
filter_queryNo
include_completedNo
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does reasonably well: it discloses the default incomplete-only filtering behavior, the 50-per-call server cap, the override precedence of next_link, and the two possible result shapes (bare list vs {items, next_link}). It omits auth/permission requirements and error behavior, but the core runtime semantics are surfaced.

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-loaded purpose sentence followed by a tidy Args block where each entry earns its place, including the non-obvious paging advice. Slightly verbose in listing defaults that also appear in the schema, but nothing is wasted.

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 tool with no output schema and no annotations, the description covers paging, filtering, defaults, and the shape of the returned value, which is what an agent needs to call it and continue paging. It stops short of describing the fields on each task object.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description compensates completely, documenting all seven parameters including defaults, the OData filter example, and the interaction rules that the schema cannot express. One minor tension: it states top's maximum as 50 while the schema allows far larger integers, so an agent gets slightly conflicting guidance on that bound.

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 opening sentence gives a specific verb and resource ('List tasks in a Microsoft To Do list') and orients the agent by pointing to graph_list_todo_lists as the source of list_id. It does not explicitly contrast itself with the planner-task sibling, but the resource is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage conditions are described at the parameter level (when include_completed=false and no filter_query, only incomplete tasks return; next_link overrides other paging args; page by raising skip in steps of top). There is no explicit statement of when to prefer this tool over graph_list_my_planner_tasks or other task-listing siblings, so usage is implied rather than fully guided.

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