list_statuses

List a project's statuses (board columns) in board order with their key, name and category (todo, in_progress, review, done). Keys are what create_issue, update_issue_status, move_issue and search_issues take as status. The category says what a status means: done = finished, everything else is open. Answers are compact JSON; pass format="text" for a readable Markdown answer. Results are paged: if the answer has a cursor, call again with it (a missing cursor means the last page) — never assume the first page is everything.

• 2026-10-02 — Answers are compact JSON by default (one document, no Markdown, nothing said twice); format="text" gives the readable Markdown without the json block. Each status is {key, name, category, color (when set)}, `default` is the key new issues start in.
• 2026-10-02 — Paged: new optional limit and cursor arguments. The answer carries the paging (total, totalApproximate, page, pages, count, limit, cursor; a missing cursor means the last page); format="text" opens with a header (Page N of M · X items · showing a–b) and ends with the next cursor or Last page.
• 2026-10-03 — Also answers structuredContent (see outputSchema); a failed call adds structuredContent.error. Text unchanged. Details: /docs/mcp, "Structured results and errors".
• 2026-10-04 — Claude Code 2.1.288+ (clientInfo claude-code): the text of a successful answer is itself up to 512 bytes, else "Result in structuredContent (N bytes)."; structuredContent and errors are unchanged. See /docs/mcp.
• 2026-10-04 — format="text" now also answers structuredContent {"text": the Markdown} (it was the JSON document), so a client that reads only structuredContent gets the Markdown it asked for.