Skip to main content
Glama

list_tasks

Read-onlyIdempotent

Find tasks on Kaiten boards by filtering board, lane, column, state, owner, responsible, tag, or query. Returns compact summaries with limit and offset pagination.

Instructions

List tasks with filters. Default page 20 (max 100). Compact summaries only.

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
tagNo
limitNo
queryNo
offsetNo
statesNo
lane_idNo
board_idNo
owner_idNo
space_idNo
column_idNo
external_idNo
responsible_idNo

Output Schema

NameRequiredDescriptionDefault
countYes
itemsYes
limitYes
offsetYes
card_idNo
_metricsNo
has_moreYes
next_offsetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior: default page size of 20, a 100 cap, and the fact that results are compact summaries rather than full task objects. It does not say how to retrieve full detail, which limits the value.

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?

Three short sentences, front-loaded with purpose, then pagination defaults, then output granularity. Nothing is padded; the only shortfall is that the brevity leaves gaps rather than that it wastes words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter listing tool, the definition is thin: filter semantics, pagination interaction between limit and offset, and how to get full task data are all absent. The presence of an output schema excuses it from describing return values, but the input side remains substantially unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 12 parameters, so the description carries the full burden and largely fails: it says 'with filters' without naming or explaining any of tag, query, states, space/board/lane/column, owner or responsible IDs. Notably the string-typed 'states' field format (single vs comma-separated) is left entirely unexplained.

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?

"List tasks with filters" states a specific verb and resource, and the name plus siblings (get_task, create_task) make the read/list intent unambiguous. It does not explicitly contrast itself with get_task, but the listing scope is clear from the wording.

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?

No guidance on when to use this versus get_task for a single task, nor on how to combine the many filters. The only steering is the implicit 'list' versus 'get' distinction an agent must supply itself.

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