delete_work_item
Deletes a work item after the person confirms; cancelling with a reason keeps it on the record instead.
Delete a work item by work_item_id, with its criteria. Its reference is never reused and its sub-tasks stay, without a parent. The removal goes through the same action the Backlog page runs and work_item.deleted goes out. The tool is destructive: a Heimdall turn pauses for the person's confirmation and an MCP client asks before sending. Prefer move_work_item to cancelled with a reason, so the record keeps the item and why it went. A staff token with work-item: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
work_item_id*stringUUID of the work item to delete.
What it returns
{ "data": { "work_item_id": "b2c3d4e5-f6a7-4b8c-9d0e-1f2a3b4c5d6e", "deleted": true }}How it fails
RESOURCE_NOT_FOUNDunknown work_item_id, or an item 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 work-item:delete.
TOKEN_MISSING_ABILITYtoken lacks work-item:delete.
How is this guide?
Last updated on