List tasks
list_tasksList, search, or count Taiga project tasks with filters for story, sprint, status, assignee, tags, and dates to see what remains, what is assigned to you, or how many tasks were finished.
Instructions
List, search or count tasks of a Taiga project: the small pieces of work a user story is split into. Reference number, title, status, assignee, and the story and sprint each task belongs to. Filter by story, sprint, status, open or closed, assignee, tag, the days they were created or finished in, or words in the text. Use it for questions such as "what is left to do on story 42" (story: 42, closed: false), "what am I working on this sprint" (sprint: "current", assigned_to_me: true) or "how many tasks did I finish this month" (assigned_to_me: true, finished_from). The heading gives the count of all matches, so for "how many" a small limit is enough. A project has many tasks, so pass at least one filter. For the stories themselves use list_user_stories; for the description and comments of one task use get_item.
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": {
"project": "<project>"
},
"name": "list_tasks"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | Only items that carry this tag, e.g. "backend". get_project lists the tags of a project. | |
| page | No | Which part of a long list, counted from 1. When an answer says more items exist, call again with the next page and the same `limit` and filters. | |
| limit | No | Most items to return in one answer (default 30, at most 100). The answer says how many more exist. | |
| story | No | Reference number of a user story, without the #: only the tasks of that story. | |
| closed | No | false: only items still open ("not done yet", "remaining"). true: only closed ones. Leave out for both. | |
| search | No | Words to look for in titles, descriptions and tags, e.g. "invoice export". An item must contain every word; a word also matches the beginning of a longer one. Use it when the user describes an item instead of giving its number. | |
| sprint | No | A sprint name from list_sprints, or "current" for the sprint running today. | |
| status | No | Exact status name, e.g. "In progress". Each project defines its own; a wrong name is answered with the valid ones. For "open" or "done" in general use `closed` instead. | |
| project | Yes | Project slug as given by list_projects, e.g. "acme-billing". Not the display name. | |
| created_to | No | Only items created on or before this day, as YYYY-MM-DD (UTC). | |
| assigned_to | No | Only items assigned to this person: full name or username as in Taiga; part of the name is enough when it fits one member only, and accents may be left out. "unassigned" for items assigned to nobody. A name that does not fit is answered with the members. For the signed-in user use `assigned_to_me`. | |
| finished_to | No | Only items closed on or before this day, as YYYY-MM-DD (UTC). Items still open are left out. | |
| created_from | No | Only items created on or after this day, as YYYY-MM-DD (UTC). | |
| finished_from | No | Only items closed on or after this day, as YYYY-MM-DD (UTC). Items still open are left out. | |
| assigned_to_me | No | true: only items assigned to the signed-in user ("my stories", "assigned to me"). |