Skip to main content
Glama

Coline

List tasks

list_tasks
Read-onlyIdempotent

Lists tasks on one board, optionally filtered by text, status or assignee.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>",
      "taskboardId": "<taskboardId>"
    },
    "name": "list_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault: every task.
queryNoWords in the title or description.
cursorNonextCursor from the previous page.
statusIdNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
taskboardIdYesBoard id from list_boards.
assigneeUserIdNo

Output Schema

NameRequiredDescriptionDefault
tasksYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only the board-scoping constraint; it says nothing about whether results are paginated (the cursor parameter implies it), ordering, or result caps, so added value beyond annotations is modest.

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?

A single well-formed sentence that front-loads the resource and scope, with the filter caveat following. Nothing is wasted, but the sentence is short enough that it leaves detail gaps rather than being maximally economical for a 7-parameter tool.

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?

Annotations and an output schema carry much of the burden, but for a 7-parameter listing tool the description omits pagination behavior (cursor/limit interplay) and default page size (limit defaults to 'every task' per schema), which the agent would need to reason about large boards.

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 71%, and the two undocumented parameters (statusId, assigneeUserId) are exactly the ones the description explains via 'filtered by ... status or assignee'. That is genuine added meaning, though it gives no value format or id examples.

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 gives a specific verb (Lists) and resource (tasks) plus a scoping constraint (on one board) and names the filter dimensions. An agent can distinguish this from list_my_tasks or list_deleted_tasks by the 'one board' scope, though no sibling is named explicitly.

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?

'Optionally filtered by text, status or assignee' implies how to narrow results, but there is no explicit when-to-use guidance, no exclusions, and no pointer to filter_tasks, search_tasks or list_my_tasks for other cases. Usage must be inferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources