Skip to main content
Glama

delete_task

Permanently removes a Lilt task using its ID or title. For repeating tasks, specify whether to skip only the current occurrence or end the whole series.

Instructions

Delete a task in Lilt (permanent). Identify it by id or title. For a repeating task, scope controls whether only this occurrence is removed (series continues with the next one) or the whole series ends.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoTask id — full UUID or a unique prefix (as shown in list_tasks, e.g. 'a1b2c3d4').
scopeNoFor repeating tasks only. 'occurrence' (default) skips this one and keeps the series; 'series' ends it.
titleNoTask title — exact (case-insensitive) or a unique partial match. Use instead of id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the critical behavior: deletion is permanent, and for repeating tasks the series either continues or ends depending on scope. It omits what happens on an ambiguous id/title match or when the task does not exist, which keeps it from a 5.

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?

Three tight sentences with no waste, and the most important fact (permanent deletion) is front-loaded before the identification and scope details.

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 destructive tool with no annotations and no output schema, the description covers the essentials: permanence, identification methods, and repeating-series semantics. It lacks only error/ambiguity handling and permission context to be fully complete.

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 all three parameters are already documented, giving a baseline of 3. The description restates the id-or-title choice and the scope consequence rather than adding new syntax or constraints, so it adds little beyond the schema.

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?

The description states a specific verb and resource ('Delete a task in Lilt') and immediately qualifies it as permanent, which distinguishes it from reversible siblings like complete_task or snooze_task. It also explains the two identification paths, so an agent knows exactly what the tool does.

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 implied by the destructive intent and by the note that permanence applies, but the description never explicitly says when to choose deletion over complete_task or update_task, nor does it state prerequisites or confirmation requirements. For a destructive operation, the guidance is adequate but thin.

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