READ

list_test_suites

A project's test suites in tree order, each with its parent, the component it covers and how many cases it holds, so an agent files a case by suite id.

Return the test suites of one project in the project's order, parents and children alike: each row carries name, description, parent_id (null at the root), component_id and component_name when the suite covers one component, and test_case_count. Nest the rows by parent_id to draw the tree. Read it to find the suite a case belongs in before you file one with create_test_case_draft, or to say which folder holds the cases a plan should pick.

Optional filters narrow the page to the suites directly under one parent_id, to the root level only, to the suites that cover one component_id, or to the suites whose name or description contain search. The suites themselves are shaped by people on the Suites tab.

Requires ability

The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.

Annotations

Read-only

It reads and never changes anything.

Arguments

project_id*string

UUID of the project whose suites to list.

parent_idstringoptional

Narrow to the suites filed directly under one suite, by its UUID.

rootbooleanoptional

True to list the suites at the root only.

component_idstringoptional

Narrow to the suites that cover one component, by its UUID.

searchstringoptional

Words the name or the description must contain.

limitintegeroptional

Suites per page (1..100, default 25).

min1max100
pageintegeroptional

1-indexed page number.

min1

What it returns

{  "data": [    {      "id": "a9b8c7d6-e5f4-4a3b-9c2d-1e0f9a8b7c6d",      "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",      "parent_id": "f1e2d3c4-b5a6-4978-8a9b-0c1d2e3f4a5b",      "component_id": "3c4d5e6f-7a8b-4c9d-8e0f-1a2b3c4d5e6f",      "component_name": "Web app",      "name": "Vouchers",      "description": "Everything the voucher wallet does at checkout.",      "position": 2,      "test_case_count": 14,      "created_at": "2026-11-04T09:00:00+00:00",      "updated_at": "2026-11-04T09:00:00+00:00"    }  ],  "meta": { "page": 1, "limit": 25, "total": 1, "has_more": false }}

How it fails

RESOURCE_NOT_FOUND

unknown project_id, or a project outside the token's scope or the person's visibility.

TOKEN_MISSING_ABILITY

token lacks test-suite:view-any.

How is this guide?

Last updated on