added 2026-10-03
List the criteria templates of a project, or of one epic (epic: its key), both kinds, in the order issues get them (project owner only). Each is {id, kind, text, types (absent: every type)}; the id is what set_criteria_templates keeps. A template is copied onto an issue when it is created, and by apply_templates of set_criteria. 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.
cursorstringoptionalCursor from `Next page` of an earlier result of this call (omit for the first page); pass it unchanged, with the same other argumentsepicstringoptionalEpic key: that epic's templates instead of the project'sformatenumoptionalAnswer format: "json" (default) is one compact JSON document; "text" is a readable Markdown answerjsontextlimitintegeroptionalHow many templates per page (1–200, default 50)projectstringrequiredProject key
Returns
One of these shapes, depending on the arguments:
Shape 1
countintegerrequiredlimitintegerrequiredtemplatesarray of object | nullrequired
Shape 2
Optional fields, when present
cursorstringoptionalepicstringoptionalThe epic key, when the templates are an epic'snotestringoptionalpageintegeroptionalpagesintegeroptionaltotalintegeroptionaltotalApproximatebooleanoptional
- 2026-10-03 — New read tool (owner): the criteria templates of a project or of one epic, both kinds, with the issue types each applies to.
- 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.