DESTRUCTIVE

delete_label

Deletes a label of a project after the person confirms; every item wearing it loses it.

Delete a label by label_id. Every item wearing it loses it. The removal goes through the same action the backlog's label manager runs and label.deleted goes out. The tool is destructive: a Heimdall turn pauses for the person's confirmation and an MCP client asks before sending. A staff token with work-item:update 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

Destructive

A client that honours annotations asks a person before running it.

Arguments

label_id*string

UUID of the label to delete.

What it returns

{  "data": {    "label_id": "5d6e7f8a-9b0c-4d1e-8f2a-3b4c5d6e7f8a",    "deleted": true  }}

How it fails

RESOURCE_NOT_FOUND

unknown label_id, or a label outside the token's scope or the person's visibility.

FORBIDDEN

the token is a client guest's, or the holder's role on the project does not carry work-item:update.

TOKEN_MISSING_ABILITY

token lacks work-item:update.

How is this guide?

Last updated on