Skip to main content
Glama

update_task

Edit an existing Lilt task by ID or title, changing only the fields you provide; use it to update status, due date, project, priority, notes, or recurrence, and clear values when needed.

Instructions

Edit a task in Lilt. Only the fields you pass are changed. Identify the task by id or title. Pass an empty string for due or project to clear them; pass recurrence 'none' to stop repeating.

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

Input Schema

NameRequiredDescriptionDefault
idNoTask id — full UUID or a unique prefix (as shown in list_tasks, e.g. 'a1b2c3d4').
dueNo
notesNoReplace the notes.
titleNoTask title — exact (case-insensitive) or a unique partial match. Use instead of id.
statusNoSetting 'done' behaves like complete_task.
projectNoExisting project name, or empty string to unfile.
intervalNo
priorityNo
weekdaysNo
new_titleNoRename the task.
recurrenceNo
monthly_anchorNo
show_days_beforeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does well on the mutation semantics that matter most (patch-style updates, empty string clears due/project, recurrence 'none' stops repetition), but says nothing about permission requirements, what happens on a failed id/title match, or whether 'done' transitions behave identically to complete_task beyond the schema note.

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 doing distinct work: purpose, patch semantics, identification method, and clearing conventions. The most error-prone instructions are front-loaded and nothing is repeated.

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?

For a 13-parameter mutation tool with no annotations and no output schema, the description covers the essentials of how to invoke it safely but leaves a large block of scheduling parameters undocumented and gives no sense of the result of an edit. Adequate, not 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 coverage is 46% across 13 parameters, so the description must compensate. It clarifies the highest-risk cases — clearing `due` and `project` with an empty string, stopping recurrence with 'none', and identifying by id or title — but leaves the linked recurrence parameters (interval, weekdays, monthly_anchor, show_days_before) entirely unexplained in both schema and description.

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?

States a specific verb and resource ("Edit a task in Lilt") and, via the patch-semantics sentence, makes clear this is an update rather than a create/delete. It does not name any sibling explicitly (e.g. complete_task, snooze_task), so differentiation is by implication from the sibling names rather than from the description.

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?

"Only the fields you pass are changed" establishes partial-update usage and the clearing conventions tell the agent how to remove values, which is genuinely useful guidance. There is no statement about when to prefer this over complete_task, reopen_task or snooze_task for status changes, so the routing decision is left to the agent.

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