Microsoft 365 MCP Server

list-plan-tasks

Read-only

Retrieve tasks from a Microsoft Planner plan to manage project workflows and track progress using Microsoft 365 services.

Instructions

Retrieve a list of plannerTask objects associated with a plannerPlan object.

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": {
      "plannerPlanId": "<plannerPlanId>"
    },
    "name": "list-plan-tasks"
  }
}

Input Schema

Name	Required	Description
`top`	No	Show only the first n items
`skip`	No	Skip the first n items
`search`	No	Search items by search phrases
`filter`	No	Filter items by property values
`count`	No	Include count of items
`orderby`	No	Order items by property values
`select`	No	Select properties to be returned
`expand`	No	Expand related entities
`plannerPlanId`	Yes	Path parameter: plannerPlanId
`fetchAllPages`	No	Automatically fetch all pages of results
`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.

First observedv0.0.0-developmentMar 25, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, covering safety and pagination aspects. The description adds no behavioral context beyond this, such as rate limits, authentication needs, or what 'plannerTask objects' entail. It doesn't contradict annotations, but fails to supplement them with useful operational details.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every part of the sentence contributes essential information.

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

Completeness3/5

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

Given the tool's complexity (12 parameters, no output schema) and rich annotations, the description is minimally adequate. It covers the basic purpose but lacks details on return format, error handling, or integration with sibling tools. For a list operation with many filtering options, more context would improve completeness, though annotations help offset some gaps.

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

Parameters3/5

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

Schema description coverage is 100%, so parameters like 'top', 'skip', 'filter', and 'plannerPlanId' are well-documented in the schema. The description adds no semantic context beyond implying a relationship to 'plannerPlan', which is already covered by the required parameter. This meets the baseline for high schema coverage without extra value.

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 description clearly states the verb ('Retrieve a list') and resource ('plannerTask objects associated with a plannerPlan object'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from sibling tools like 'list-planner-tasks' (which appears to be a duplicate name) or 'get-planner-task', missing an opportunity for full sibling differentiation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid plannerPlanId), compare it to similar tools like 'get-planner-task' for single tasks, or specify use cases like filtering tasks by status. This leaves the agent without contextual usage direction.

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

Deploy Server