Skip to main content
Glama

List tasks

list_tasks
Read-onlyIdempotent

List accessible tasks, optionally in one project. Returns due dates, status, assignees, and source links. Keep ordering and filters unchanged across pages.

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
afterNoPagination cursor from the previous nextCursor. Keep filters and ordering unchanged; omit for the first page.
limitNoMaximum number of items to return, from 1 to 100. Defaults to 50.
orderNoResult ordering. Defaults to most recently updated first. Keep the same order while paging.UPDATED_DESC
queryNoSearch text. List tools filter names/titles; search queries indexed workspace content.
dueAfterNoInclusive earliest deadline, as ISO 8601 with timezone.
priorityNoPriority: 0 Low, 1 Normal, 2 High, 3 Urgent. For updates, null clears it.
dueBeforeNoInclusive latest deadline, as ISO 8601 with timezone.
projectIdNoExisting accessible project ID returned by list_projects.
assigneeIdNoFilter tasks by this existing user ID.
stateProjectIdNoTask status ID from list_project_statuses for the destination project.

Output Schema

NameRequiredDescriptionDefault
itemsYesAccessible records on this page.
nextCursorYesPass as after for the next page; null when this page has no continuation cursor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / assigneeId
      Added value: +{
      +  "description": "Filter tasks by this existing user ID.",
      +  "maxLength": 100,
      +  "minLength": 1,
      +  "pattern": "^[A-Za-z0-9_-]+$",
      +  "type": "string"
      +}
    • addedInput schema / properties / dueAfter
      Added value: +{
      +  "description": "Inclusive earliest deadline, as ISO 8601 with timezone.",
      +  "format": "date-time",
      +  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
      +  "type": "string"
      +}
    • addedInput schema / properties / dueBefore
      Added value: +{
      +  "description": "Inclusive latest deadline, as ISO 8601 with timezone.",
      +  "format": "date-time",
      +  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
      +  "type": "string"
      +}
    • addedInput schema / properties / priority
      Added value: +{
      +  "description": "Priority: 0 Low, 1 Normal, 2 High, 3 Urgent. For updates, null clears it.",
      +  "maximum": 3,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / query
      Added value: +{
      +  "description": "Search text. List tools filter names/titles; search queries indexed workspace content.",
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / stateProjectId
      Added value: +{
      +  "description": "Task status ID from list_project_statuses for the destination project.",
      +  "maxLength": 100,
      +  "minLength": 1,
      +  "pattern": "^[A-Za-z0-9_-]+$",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restatement. The description adds the pagination-stability requirement across pages, but the listed return fields (due dates, status, assignees, source links) duplicate what the output schema already provides, so added value 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?

Three short sentences, front-loaded with scope and followed by return shape and paging discipline; no filler. The mid-sentence clause about paging repeats a constraint already stated per-parameter, but the repetition is cheap and reinforces a real failure mode.

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?

Ten optional parameters, full schema coverage, an output schema, and rich annotations mean the structured data carries most of the burden, and the description covers scope, return contents and paging. The remaining gap is sibling differentiation against list_figma_tasks, which an agent must resolve unaided.

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% and each parameter carries its own description, so the baseline is 3; the description nudges above that by reinforcing the project scoping semantics and the invariant that filters and ordering must stay fixed across pages, which is a correctness-relevant usage constraint rather than a schema restatement.

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?

States a specific verb and resource ('List accessible tasks') plus scope ('optionally in one project'), which is clearly actionable. It misses the one distinction that matters here: the sibling list_figma_tasks likely returns Figma-originated tasks, and the description does nothing to separate the two.

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 in one project' and the paging instruction imply usage context, but there is no explicit when-to-use guidance, no mention of when to prefer search or list_figma_tasks, and no stated prerequisites beyond 'accessible'.

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.