Skip to main content
Glama

graph_list_my_planner_tasks

List Microsoft Planner tasks assigned to you, with paging options to fetch results in batches or continue from a next link.

Instructions

List Microsoft Planner tasks assigned to the user.

Planner tasks live on plans owned by Microsoft 365 groups, so this is separate from Microsoft To Do. Requires the Tasks.Read permission.

Args: top: Maximum number of tasks to return (default 25, maximum 50). 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "graph_list_my_planner_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
skipNo
next_linkNo
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does substantial work: it discloses the auth requirement (Tasks.Read), the server-side page cap of 50, how to page with skip, and that next_link overrides the other paging arguments. It does not say what happens on an expired/permalformed next_link or what a task record contains, leaving some behavioral gaps.

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 with the purpose and the critical Planner-vs-To-Do distinction before the args block. A few clauses restate schema defaults (25, 0, false), which is minor redundancy, but the args list is scannable and nothing important is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description correctly covers return shape (bare list vs {items, next_link}), the paging model, auth, and the result cap. For a four-parameter, read-only list tool this is sufficient for an agent to call it correctly and paginate.

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 description coverage is 0%, so the description must compensate and does: all four parameters get meaning beyond their types, including the real cap of 50 per call, the paging recipe (raise skip in steps of top), next_link's precedence over paging args, and the exact shape of the return when include_next_link is true. This is materially richer than the bare schema, whose maximum of 9007199254740991 would otherwise mislead about paging limits.

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 and resource ("List Microsoft Planner tasks assigned to the user") and immediately scopes the resource to Planner's group-owned plans. It explicitly names the adjacent sibling (Microsoft To Do) as a different tool, so an agent can route correctly without opening either schema.

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?

Provides a clear selection cue by distinguishing Planner tasks from Microsoft To Do, and states the required Tasks.Read permission as a precondition. It lacks an explicit "do not use this when..." exclusion or a named alternative for other task sources, so it stops short of the top band.

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