Skip to main content
Glama

graph_delete_todo_task

Delete a task from a Microsoft To Do list by providing the list ID and task ID, removing unwanted to-do items from the specified list.

Instructions

Delete a task from a Microsoft To Do list.

Args: list_id: The task list ID (from graph_list_todo_lists). task_id: The task ID to delete.

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>",
      "task_id": "<task_id>"
    },
    "name": "graph_delete_todo_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
list_idYes
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden and it discloses almost nothing: it does not say whether deletion is irreversible, whether the task moves to deleted items and can be restored, what permissions are required, or what a successful/failed response looks like. Only the implicit destructiveness of the verb 'delete' is conveyed.

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?

Two sentences plus a short args block, front-loaded with the action and resource; nothing is padded. The task_id line is nearly redundant but the whole remains tight for its size.

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 two-parameter leaf operation with no output schema, the essentials (which task in which list) are covered. What's missing is destructive-operation context — reversibility and required permissions — which for a delete tool is a real gap, keeping it below a 5.

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 0%, so the description must compensate and it does partially: list_id is explained as the task list ID with a pointer to graph_list_todo_lists, and task_id as the ID to delete. However, 'The task ID to delete' is tautological and no ID format (GUID) or validation expectations are given.

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 states a specific verb and resource: 'Delete a task from a Microsoft To Do list.' That is enough to distinguish it from creation and update siblings, though it does not contrast against other delete_* siblings or confirm scope (e.g., permanent vs. recycle-bin removal).

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 is only implied by the verb 'delete'; there is no explicit when-to-use or when-not guidance, no confirmation/precondition advice. The one useful hint is provenance for list_id ('from graph_list_todo_lists'), which tells the agent how to obtain it.

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