Skip to content

MCP Tools: Lists ​

list_lists ​

Lists the user has access to. read · follower

ParameterTypeDefaultDescription
statusstring–open, inprogress, done, completed, closed, archived
lifecyclestring–active, archived, trashed
searchstring–Search in name and description
includeTemplatesbooleanfalseInclude templates
excludeCompletedbooleanfalseHide completed/closed lists
limitnumber50Number of results
offsetnumber0Results to skip

Response: { lists, total, limit, offset, has_more }.

get_list ​

List including its items. read · follower

ParameterTypeDefaultDescription
listIdstring (required)–UUID or SID
includeItemsbooleantrueInclude items
includeArchivedbooleanfalseInclude archived items
compactbooleanfalseOnly id, sid, parent, text, status, priority, target_date

create_list ​

Create a new list. write · user

ParameterTypeDescription
namestring (required)Name (min. 1 character)
descriptionstringDescription
typestringType
statusstringInitial status
colorstringColor
tagsstring[]Tags

update_list ​

Update a list. write · user

ParameterTypeDescription
listIdstring (required)UUID or SID
namestringNew name
descriptionstringNew description
statusstringNew status
lifecyclestringNew lifecycle state
colorstringNew color
lockedbooleanLock/unlock
tagsstring[]New tags

delete_list ​

Move a list to the trash. destructive · admin

ParameterTypeDescription
listIdstring (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
ParameterTypeDefaultDescription
listIdstring (required)–UUID, SID or project number
includeSubprojectsbooleanfalseAlso 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
ParameterTypeDefaultDescription
listIdstring (required)–UUID, SID or project number
daysnumber (7–90)30Burn-up window
completedFromstring (ISO)30 days before completedToStart of the completed-tasks period (inclusive)
completedTostring (ISO)nowEnd of the completed-tasks period (exclusive)
maxCompletednumber (1–200)50Max completed tasks to list

Response:

  • project — name, number, status, start/end (timeframe), completed_at
  • totals — across the project and all sub-projects: tasks, open, done, overdue, completed in 7/30 days, next due, last activity, by_status
  • subprojects — count, without access, by status and rows: per direct sub-project the same totals over its subtree plus planned end
  • burnup — weekly points { day, total, done }
  • people — open/overdue tasks per person, name: null = unassigned
  • completed — 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.