delete_raid_item
Deletes a RAID item after the person confirms; closing it keeps it on the log instead.
Delete a RAID item by raid_item_id. Its reference is never reused. The removal goes through the same action the RAID Log page runs and raid_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 closing an item with update_raid_item, so the log keeps what the team watched. A staff token with raid: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
raid_item_id*stringUUID of the RAID item to delete.
What it returns
{ "data": { "raid_item_id": "c9d0e1f2-a3b4-4c5d-8e6f-7a8b9c0d1e2f", "deleted": true }}How it fails
RESOURCE_NOT_FOUNDunknown raid_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 raid:delete.
TOKEN_MISSING_ABILITYtoken lacks raid:delete.
How is this guide?
Last updated on