Skip to main content
Glama

Weft

by com.letsweft
OverviewDiscussionsAdmin

List Tasks

list_tasks
Read-only

Use this when the user wants tasks scoped to a specific column, sprint or dates. Without filters, returns every task on the board (capped at 200 — filter by columnId/sprintId if truncated). Sprint-scoped listing includes the sprint's archived (swept) tasks, so completed sprints show their full history. With from/to it reads the calendar: every task due, starting or running inside those days, in date order — use it for 'what is due next week?' or 'what did I have on the 3rd?'. Prefer get_board_state when the user wants a general overview.

Input Schema

NameRequiredDescriptionDefault
toNoCalendar: last day to include, inclusive. Defaults to six weeks after `from`.
fromNoCalendar: first day to include (ISO date-time, only the date is used). Use with `to`.
projectNoFilter by project — name (case-insensitive) or ID. Pass 'none' to get tasks that belong to no project
assigneeNoFilter by executor: a member's name or email, 'me' (tasks assigned to you, the calling agent), or 'none' (unassigned)
columnIdNoFilter by column ID
sprintIdNoFilter by sprint ID
createdSourceNoFilter by who created the task: 'user' = a human in the app, 'mcp' = an AI client over MCP (Claude, ChatGPT, Cursor, …)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / from
      Added value: +{
+  "description": "Calendar: first day to include (ISO date-time, only the date is used). Use with `to`.",
+  "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 / to
      Added value: +{
+  "description": "Calendar: last day to include, inclusive. Defaults to six weeks after `from`.",
+  "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"
+}
  2. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With readOnlyHint/destructiveHint already declaring the safety profile, the description goes further: a 200-result cap with a documented remedy, the non-obvious inclusion of archived ('swept') tasks in sprint-scoped listings, and the semantics of date-range matching (due, starting or running inside the window) plus date ordering. These are behaviors nothing in the annotations or schema discloses.

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?

Four dense sentences, front-loaded with the trigger condition before the fallback and alternative-tool advice. Every clause carries operational information; only the sprint-archived-tasks aside is slightly parenthetical, keeping it just short of a 5.

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

Completeness5/5

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

All seven optional parameters are documented in the schema, there is no output schema to explain, and the description fills the remaining gaps an agent needs: default scope, truncation handling, and how filters combine. Nothing required to call this correctly is missing.

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 parameter documentation baseline is met structurally. The description still adds genuine meaning: it explains that from/to read as a calendar window with a six-week fallback and clarifies the interaction between from/to and result ordering, which the schema descriptions only partially convey.

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

Purpose5/5

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

States a specific verb and resource ('tasks'), plus the scoping axes (column, sprint, dates) and the default behavior when no filters are given. It explicitly contrasts itself with the sibling get_board_state, so an agent can select between them without opening either schema.

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

Usage Guidelines5/5

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

Opens with an explicit when-to-use clause, names the alternative ('Prefer get_board_state when the user wants a general overview'), and gives sample phrasings ('what is due next week?') that map user intent to this tool. It also instructs the agent to narrow filters when the 200 cap truncates results.

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

All Weft toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources