Skip to main content
Glama

Delete To Do List

delete_todo_list
Destructive

Permanently deletes a Microsoft To Do list and all its tasks; use force to remove lists that still contain tasks. Built-in Tasks and Flagged Emails lists cannot be deleted.

Instructions

Delete a To Do list and every task in it. There is no API to restore it, so treat it as permanent. A list that still holds tasks needs force: true. The built-in Tasks and Flagged Emails lists can't be deleted.

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": "delete_todo_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoRequired when the list still holds tasks, which are deleted with it
list_idYesTo Do list ID, as list_todo_lists returns it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description adds real context beyond them: irreversibility ('no API to restore it, so treat it as permanent'), the cascade behavior, and the protected built-in lists. That is exactly the extra information an agent needs before an unrecoverable call.

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?

Four short sentences, each carrying distinct information: effect, irreversibility, force requirement, and protected lists. Irreversibility is front-loaded right after the action statement.

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?

Only two parameters, no nested objects and no output schema, so the burden is light and the description covers the destructive behavior and its limits well. It says nothing about the return value or error shape for blocked deletions, a minor gap.

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 coverage is 100% and the schema already documents force as required when tasks remain, so the description largely restates it. It adds the useful constraint that built-in lists are undeletable, but no new syntax or format for either parameter.

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 plus the cascade scope: 'Delete a To Do list and every task in it.' The cascade wording implicitly separates it from delete_todo_task, which removes a single task rather than a whole list.

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?

Gives explicit preconditions and exclusions: a list holding tasks requires force: true, and the built-in Tasks and Flagged Emails lists cannot be deleted at all. It does not name an alternative tool, but the when/when-not conditions are clear enough to act on.

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