DESTRUCTIVE

delete_design_reference

Deletes a design reference of a project after the person confirms; the design itself is untouched.

Delete a design reference by design_reference_id. Only the link goes; the design lives where it lived. The removal goes through the same action the Designs page runs and design_reference.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 design-reference: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.

The REST endpoint and this tool share one action, so validation, permissions and events are identical.

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

design_reference_id*string

UUID of the design reference to delete.

What it returns

{  "data": {    "design_reference_id": "3b4c5d6e-7f8a-4b9c-8d0e-1f2a3b4c5d6e",    "deleted": true  }}

How it fails

RESOURCE_NOT_FOUND

unknown design_reference_id, or a reference 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 design-reference:delete.

TOKEN_MISSING_ABILITY

token lacks design-reference:delete.

How is this guide?

Last updated on