update_glossary_term
Changes a glossary term in part and moves it along its review when a status is sent.
Change a glossary term by glossary_term_id with any of term, definition (HTML), aliases and related_term_ids (each replaces its list), source and status (draft, in_review, approved or deprecated; a move the lifecycle allows from where the term stands). A field left out keeps its value; a field sent as null is cleared. The fields go through the same action the Dictionary page runs and the status through its own move, so glossary_term.updated and, on a move, glossary_term.status_changed go out. A staff token with glossary: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 actions as
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
A client that honours annotations asks a person before running it.
Arguments
glossary_term_id*stringUUID of the glossary term.
termstringoptionalThe word, as the project uses it, 1 to 80 characters.
definitionstringoptionalWhat it means, as HTML.
aliasesstring[]optionalThe other names it goes by.
related_term_idsstring[]optionalUUIDs of the terms of the same project it leans on.
sourcestringoptionalWhere the definition comes from: a document, a person, a standard.
statusstringoptionalWhere the term stands in review; a move the lifecycle allows.
draftin_reviewapproveddeprecatedWhat it returns
{ "data": { "id": "7a8b9c0d-1e2f-4a3b-8c4d-5e6f7a8b9c0d", "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13", "term": "Drop-off", "definition": "<p>A customer leaving laundry at the shop counter rather than booking a pickup.</p>", "aliases": ["Walk-in", "Counter order"], "related_term_ids": ["8b9c0d1e-2f3a-4b4c-8d5e-6f7a8b9c0d1e"], "source": "The shop's own words", "status": "approved", "position": 1, "created_at": "2026-10-28T09:30:00+00:00", "updated_at": "2026-10-28T15:12:00+00:00" }}How it fails
VALIDATION_FAILEDa field outside its limits, a term another entry of the project already uses, a related term that is not the project's, a status outside the four, or a move the lifecycle does not allow from where the term stands.
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:update.
TOKEN_MISSING_ABILITYtoken lacks glossary:update.
How is this guide?
Last updated on