MCP for Microsoft To Do

batch_delete_tasks

DestructiveIdempotent

Delete up to 100 Microsoft To Do tasks from specified lists in a single batch HTTP call, saving time by reducing multiple API requests.

Instructions

Delete several tasks in a single $batch HTTP call (up to 100 items).

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": {
      "items": "<items>"
    },
    "name": "batch_delete_tasks"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes
`verbose`	No	If true: returns full JSON. Otherwise: compact text format (default, saves tokens).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1May 5, 2026

TDQS

B3.4/5.0

Behavior2/5

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

Only mentions batch HTTP call and limit; does not add behavioral info beyond annotations (destructive, idempotent).

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?

Single sentence, front-loaded, no fluff.

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?

Adequate for simple tool but missing parameter guidance and behavioral nuance; output schema absent.

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

Parameters1/5

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

No description of parameters; schema has 50% coverage, but description fails to clarify required 'items' structure.

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?

Clear verb 'delete', resource 'tasks', and constraint 'batch up to 100 items' differentiate from siblings like 'delete_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?

Implicitly suggests use for bulk deletion; lacks explicit when-not-to-use but context is clear.

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