delete_use_case
Deletes a use case and its steps after the person confirms; deprecating keeps it on the record instead.
Delete a use case by use_case_id, with its steps. Its reference is never reused. The removal goes through the same action the Use Cases page runs and use_case.deleted goes out. The tool is destructive: a Heimdall turn pauses for the person's confirmation and an MCP client asks before sending. Prefer moving a use case to deprecated with update_use_case, so the record keeps the flow. A staff token with use-case:delete on the project is needed.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Fires one event
Delivered to every endpoint subscribed to it once the change is made.
Annotations
A client that honours annotations asks a person before running it.
Arguments
use_case_id*stringUUID of the use case to delete.
What it returns
{ "data": { "use_case_id": "e5f6a7b8-c9d0-4e1f-8a2b-3c4d5e6f7a8b", "deleted": true }}How it fails
RESOURCE_NOT_FOUNDunknown use_case_id, or a use case outside the token's scope or the person's visibility.
FORBIDDENthe token is a client guest's, or the holder's role on the project does not carry use-case:delete.
TOKEN_MISSING_ABILITYtoken lacks use-case:delete.
How is this guide?
Last updated on