MCP Tools: Lists
list_lists
Lists the user has access to. read · follower
| Parameter | Type | Default | Description |
|---|---|---|---|
status | string | – | open, inprogress, done, completed, closed, archived |
lifecycle | string | – | active, archived, trashed |
search | string | – | Search in name and description |
includeTemplates | boolean | false | Include templates |
excludeCompleted | boolean | false | Hide completed/closed lists |
limit | number | 50 | Number of results |
offset | number | 0 | Results to skip |
Response: { lists, total, limit, offset, has_more }.
get_list
List including its items. read · follower
| Parameter | Type | Default | Description |
|---|---|---|---|
listId | string (required) | – | UUID or SID |
includeItems | boolean | true | Include items |
includeArchived | boolean | false | Include archived items |
compact | boolean | false | Only id, sid, parent, text, status, priority, target_date |
create_list
Create a new list. write · user
| Parameter | Type | Description |
|---|---|---|
name | string (required) | Name (min. 1 character) |
description | string | Description |
type | string | Type |
status | string | Initial status |
color | string | Color |
tags | string[] | Tags |
update_list
Update a list. write · user
| Parameter | Type | Description |
|---|---|---|
listId | string (required) | UUID or SID |
name | string | New name |
description | string | New description |
status | string | New status |
lifecycle | string | New lifecycle state |
color | string | New color |
locked | boolean | Lock/unlock |
tags | string[] | New tags |
delete_list
Move a list to the trash. destructive · admin
| Parameter | Type | Description |
|---|---|---|
listId | string (required) | UUID or SID |
get_list_stats
Statistics for a project. Only real tasks count — no files, AI chats or info-column boxes. Tasks without a status count as open.
read · follower| Parameter | Type | Default | Description |
|---|---|---|---|
listId | string (required) | – | UUID, SID or project number |
includeSubprojects | boolean | false | Also count all sub-projects (any depth); sub-projects you cannot access appear only as a count in subprojects.without_access |
Response: { list, scope, statistics: { total, open, done, overdue, completion_rate, by_status, next_due, last_activity, completed_last_7_days, completed_last_30_days }, subprojects? }. by_status uses the real statuses (open, inprogress, review, onhold, done, closed, … and none for no status).
get_project_report
Everything for a status report on a project including its sub-projects in one call — the same numbers as the project report in the app.
read · follower| Parameter | Type | Default | Description |
|---|---|---|---|
listId | string (required) | – | UUID, SID or project number |
days | number (7–90) | 30 | Burn-up window |
completedFrom | string (ISO) | 30 days before completedTo | Start of the completed-tasks period (inclusive) |
completedTo | string (ISO) | now | End of the completed-tasks period (exclusive) |
maxCompleted | number (1–200) | 50 | Max completed tasks to list |
Response:
project— name, number, status,start/end(timeframe),completed_attotals— across the project and all sub-projects: tasks, open, done, overdue, completed in 7/30 days, next due, last activity,by_statussubprojects— count, without access, by status androws: per direct sub-project the same totals over its subtree plus planned endburnup— weekly points{ day, total, done }people— open/overdue tasks per person,name: null= unassignedcompleted— completed in the period:{ date, project, ref, text, people }
If one part fails (e.g. the burn-up), it is null or { error } — the rest still arrives. Not in the agent profile; reach it there via list_liza_tools / call_liza_tool.