Skip to main content
Glama

list_tasks

Retrieve and filter tasks as compact lines grouped under project headers, combining status, assignee, project, label, due date, and readiness filters.

Instructions

Tasks as compact lines under [project] headers. Filters AND together.

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
dueNooverdue, today, week, any, none
teamNoprojects shared with this team
textNoall words in title, description or comments
limitNodefault 50
readyNoonly todo tasks with no unfinished blockers
labelsNomust have all
statusNoopen (default), todo, doing, done, all
changedNosince YYYY-MM-DD or Nd; newest first, any status
projectNopath or id, includes sub-projects
assigneeNousername or me
due_beforeNoYYYY-MM-DD
priority_minNo1-5

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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 burden. It does disclose the return format (compact lines grouped under project headers), which is valuable given there is no output schema, but it says nothing about read-only semantics, result volume, or how the default limit of 50 behaves in practice.

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 short sentences with no wasted wording, and the output-shape information is front-loaded. It is arguably over-compressed: the terseness leaves gaps that a slightly longer description could have closed at little cost.

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 12-parameter tool with no annotations and no output schema, the description covers only output format and filter combination. It says nothing about ordering across filters, volume, or how the many optional filters interact beyond AND, which leaves the definition thin relative to the tool's complexity.

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. The description goes beyond it by stating that filters combine with AND, which clarifies cross-parameter interaction the individual schema descriptions do not spell out.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence "Tasks as compact lines under [project] headers" describes the response shape more than the action, and it never states a verb or distinguishes this from siblings like get_task or inbox. An agent can infer a filtered task listing from the name plus schema, but the description alone is vague about what the tool actually does.

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

Usage Guidelines2/5

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

"Filters AND together" is a useful invocation rule that prevents a common mistake, but there is no when-to-use guidance, no exclusions, and no comparison to alternatives such as inbox or get_task. The agent is left to infer the appropriate context from parameter names.

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