delete_glossary_term
Deletes a glossary term after the person confirms; deprecating keeps the word on the record instead.
Delete a glossary term by glossary_term_id. The removal goes through the same action the Dictionary page runs and glossary_term.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 retired word to deprecated with update_glossary_term, so the record keeps what the project used to call things. A staff token with glossary: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
glossary_term_id*stringUUID of the glossary term to delete.
What it returns
{ "data": { "glossary_term_id": "7a8b9c0d-1e2f-4a3b-8c4d-5e6f7a8b9c0d", "deleted": true }}How it fails
RESOURCE_NOT_FOUNDunknown glossary_term_id, or a term 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 glossary:delete.
TOKEN_MISSING_ABILITYtoken lacks glossary:delete.
How is this guide?
Last updated on