Skip to main content
Glama

list_tasks

Read-onlyIdempotent

Retrieve and filter tasks by project, board, assignee, status, labels, overdue status, or search text, with sorting and pagination for task queries.

Instructions

List tasks with filters. The main task query tool.

Where to look (pick one):

  • project="" every task of that project; project="all" = every open project

  • scope="mine" (default) tasks assigned to me + my personal tasks

  • scope="outbox" tasks I created for other people

  • scope="everything" inbox + outbox + every open project

Filters (combine freely, applied exactly): board (title/id, needs project), assignee (name/id/"me"), unassigned, owner (creator), label (title/id), status "open"|"done"|"all", overdue_only, query (words that must all appear in title/notes/ checklist; Persian/Arabic letter variants match).

sort: "deadline" (default; overdue first), "board" (kanban order, default for a project), "modified", "created". Paginated: returns total, has_more and next_offset.

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
sortNo
boardNo
labelNo
limitNo
ownerNo
queryNo
scopeNo
offsetNo
statusNoopen
projectNo
assigneeNo
unassignedNo
notes_charsNo
overdue_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower; the description still adds useful context such as exact filter combination semantics, sort defaults ('deadline', overdue first; 'board' default for a project), and pagination fields returned. Undocumented are result-size controls and whether large result sets are truncated aside from has_more.

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?

Section headers ('Where to look', 'Filters', sort, pagination) front-load the decision-critical scoping choice before the long filter list, and each line carries distinct information. It is dense but organized, with only minor terseness in the sort and pagination lines.

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?

With an output schema present, return values needn't be spelled out, and the description still names total, has_more, and next_offset as pagination output. For a 14-parameter query tool it covers almost all decision-relevant semantics, missing only explicit limit/offset and notes_chars documentation.

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 description coverage is 0% across 14 parameters, so the description carries the full burden and mostly succeeds: it explains project, all three scope values with defaults, board, assignee (name/id/'me'), unassigned, owner, label, status open/done/all, overdue_only, query with letter-variant matching, and sort values with defaults. It leaves limit, offset, and notes_chars undocumented, which are the notable gaps for a paginated tool.

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 opening 'List tasks with filters' plus 'The main task query tool' gives a specific verb and resource and positions it as the default query entry point. It does not explicitly differentiate from siblings like search_tasks or list_my_tasks, so the agent must infer the boundary from scope semantics alone.

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?

The 'Where to look (pick one)' block with explicit scope values and defaults, plus the note that filters 'combine freely, applied exactly', gives strong when-to-use guidance for the main query modes. It stops short of stating exclusions such as when a different task-search sibling is preferable.

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