Skip to main content
Glama

list_tasks

Retrieve your Lilt tasks with IDs, filtered by status, project, or due date, to use with complete, update, or delete task actions.

Instructions

List the user's tasks in Lilt with their ids. By default shows open tasks only (To Do + In Progress). Use the returned [id] prefix with complete_task / update_task / delete_task.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows. Default 50.
statusNoFilter by status. Default: open tasks (todo + in-progress).
projectNoOnly tasks in this project (case-insensitive).
overdue_onlyNoOnly tasks past their due date.
includeSnoozedNoInclude currently snoozed open tasks. Default false.
due_within_daysNoOnly tasks due within N days (0 = today). Overdue tasks are always included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the default status filter and the '[id]' prefix format returned for downstream calls, but says nothing about result ordering, truncation when limit is hit, or what fields come back per task — meaningful gaps for a list tool with no output schema.

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?

Two tightly written sentences with the scope and default behavior front-loaded, followed by the actionable follow-up hint. No filler or repetition.

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 six-parameter, zero-annotation, no-output-schema tool, the description covers purpose, defaults, and ID usage but leaves the return shape largely unexplained beyond 'with their ids'. Ordering and pagination limits are left to be discovered at call time.

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 every one of the six parameters is already documented in the schema, including the status default and limit default. The description restates the status default rather than adding new meaning, so the baseline of 3 applies.

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 opens with a specific verb and resource ('List the user's tasks in Lilt with their ids'), which cleanly separates it from list_habits and list_projects by resource alone. It stops short of explicitly naming a sibling it is not, so it lands at clear-but-not-fully-differentiated.

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?

It states the default filter behavior ('By default shows open tasks only (To Do + In Progress)') and routes the agent forward by saying to use the returned [id] prefix with complete_task / update_task / delete_task. That is strong chaining guidance, though it gives no explicit when-not or mention of list_habits/list_projects as adjacent choices.

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