MCP Tools: Lists
Last updated 18 days ago
MCP Tools: Lists
list_lists
Lists the user has access to. read · follower
Response: { lists, total, limit, offset, has_more }.
get_list
List including its items. read · follower
create_list
Create a new list. write · user
update_list
Update a list. write · user
delete_list
Move a list to the trash. destructive · admin
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 · followerResponse: { 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 · followerResponse:
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.
Was this helpful?
Still need help? Ask the team