list_notifications

List your Sprintree inbox, newest first: mentions, assignments, comments and replies on issues you follow, status changes, edits of issues you follow (title, description, priority, labels, type, parent; consecutive edits by one person are merged into one entry), new issues in projects you watch, and project invitations. Each entry shows its kind, who did it and what changed, the project, the issue key and title, a comment excerpt, when it happened, whether it is read, and its notification id (for mark_notifications_read). Unread only by default. Use get_issue_details with the issue key for the full context. 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-04 — New kind review_requested (asked you to review it); the answer to your request arrives as an edit (approved it, requested changes).
• 2026-10-01 — Notifications you marked Done or snoozed are hidden (and do not count as unread) unless include_done / include_snoozed are set; entries show snoozed until / done.
• 2026-10-01 — New `view` parameter (inbox, snoozed, done): snoozed lists only what is still snoozed, soonest return first; done only what you marked Done, latest first. New activity by someone else on an issue brings its snoozed notifications back.
• 2026-10-01 — unread_only now defaults to false in the snoozed view and is ignored in the done view (Done rows are always read, so the default used to list nothing). A `before` cursor only works in the view it came from (else invalid_cursor).
• 2026-10-02 — The header gives the total (counted once, up to 1000: `1000+ notifications`) and the page; the cursor argument replaces before (before still works, and so does a bare notification id); the footer says `Next page: cursor=` or `Last page.`.
• 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 notification is {id, kind, at (seconds), read (only when true: the default inbox lists the unread ones), state (done or snoozed until …), issue or page (KEY/N; then issue is empty), project, by (username), text (absent when the kind says it: assigned, comment, reply), excerpt, comment (id), redacted}; the titles are in `issues` ({key: title}, cut at 60 characters) and `page_titles` ({KEY/N: title}), said once each; unread is the count of the whole inbox. 15 per page by default (limit up to 100).
• 2026-10-08 — Rows about a page have page (KEY/N) and no issue; the page titles are in the new `page_titles` map.
• 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.