manage_test_lifecycle

Manage a test's lifecycle state: trash, restore, archive, or unarchive.

Destructive · Writes data · Calls external systems. This tool can modify or delete data. Review the arguments before letting an agent call it.

Parameters

Field	Type	Required	Description
`acknowledge`	boolean	No	Must be true for destructive actions (trash, archive). Also resets the lifecycle edit budget when the limit is reached
`action`	string (trash \| restore \| archive \| unarchive)	Yes	Lifecycle action: trash, restore, archive, unarchive
`kind`	number	No	1 = regular test (default), 2 = reusable V2 component
`test_id`	number	Yes	Test id

Example arguments

Illustrative arguments an agent supplies when calling this tool:

{
  "action": "trash",
  "test_id": 0
}

Description

- trash: soft-delete to the product's test-trash collection (reversible via restore)
- restore: pull a trashed test back out of trash
- archive: mark a test as archived (keeps it visible but inactive)
- unarchive: reactivate an archived test

Requires acknowledge=true for destructive actions (trash, archive). Edit-budget gated.

What's next?

All MCP tools

Browse the full tool reference by category.

Connect a client

Point Claude, Cursor, or Claude Code at the server.