Skip to main content
Glama

Delete a task

delete_task
DestructiveIdempotent

Delete ONE task by id (from get_tasks). On a repeating task, scope "occurrence" (the default) removes only one day (date, default today) and keeps the series; "series" deletes the whole repeating task. Use delete_inbox_item for Inbox items and delete_routine for routines. Returns {id, deleted:true}, or {deleted:false, scope:"occurrence", excludedDate} for one day; not_found means nothing changed. A deleted task cannot be restored. Preview rule: if this is the second task or routine change within about 90 seconds, nothing is saved and the result is needs_preview with the pending and saved changes - show them to the user and call again with confirm:true only after they agree.

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": {
      "id": "<id>"
    },
    "name": "delete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe task id from get_tasks, e.g. "aB3dE9".
dateNoWith scope "occurrence": the day to remove, YYYY-MM-DD. Default: the user's local today.
scopeNoRepeating tasks only: "occurrence" (default) = just one day, "series" = the whole repeating task. Ignored for one-off tasks.
confirmNoSet true ONLY after the user has seen and approved this change in a preview you showed them (needed when a request changes more than one task or routine). Never set it on your own. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructive=true and idempotent=true, but the description adds material behavior beyond them: irreversibility ("A deleted task cannot be restored"), the partial-deletion return shape {deleted:false, scope:"occurrence", excludedDate}, the not_found no-op semantics, and the needs_preview interception flow with pending/saved changes. That is exactly the context an agent needs before performing an irreversible write.

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 core action, then scoping, then alternatives, then return/confirmation behavior — a logical order with no filler sentences. It is dense and long-ish, packing return shapes and the preview rule into single clauses, but every sentence carries operational information rather than restating the name.

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 carries the return-value burden and does so: success shape {id, deleted:true}, the occurrence-exclusion shape, not_found, and needs_preview with pending/saved. For a destructive, idempotent, low-parameter tool, nothing an agent needs in order to call it safely is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3 and the schema already documents id, date, scope, and confirm. The description still adds meaning beyond it by giving the concrete ~90-second threshold that triggers needs_preview and describing the pending/saved payload the agent must surface to the user, which sharpens how confirm should be used. Remaining param detail (YYYY-MM-DD format, default today) is a restatement of the schema, keeping this below 5.

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?

Opens with a specific verb and resource plus scope emphasis: "Delete ONE task by id (from get_tasks)." It immediately disambiguates the two deletion modes ("occurrence" vs "series") and names the sibling deleters for other resource types, so an agent can tell it apart from delete_inbox_item and delete_routine without opening any schema.

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

Usage Guidelines5/5

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

Explicit routing: "Use delete_inbox_item for Inbox items and delete_routine for routines." It also states exactly when to escalate to confirm:true (second task/routine change within ~90 seconds, only after the user approves a shown preview) and when scope "series" applies instead of the default occurrence. Both the alternative-tool condition and the confirmation condition are given, not inferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources