/technology/ai/google). This tool manages the catalog — the definitions themselves. To assign or remove tags on documents, use the documents tool.
New to tags? See Tags for the mental model — what tags are, how hierarchy works, and how they differ from folders.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
action | enum | Yes | list, create, delete, or update |
tagId | UUID | Conditional | Required for delete and update |
tagPath | string | Conditional | Required for create — e.g., "/technology/ai/google" |
tagDescription | string | null | No | Description for create or update |
tagColor | string | null | No | Hex color for create or update (e.g., "#3B82F6") |
tagDisplayName | string | null | No | Human-readable name — shown in UI instead of path segment. For create or update |
filesystem | string | No | Filesystem slug — optional for create when you have multiple filesystems |
Actions
| Action | tagId | tagPath | Notes |
|---|---|---|---|
list | — | — | Returns all tags in the workspace |
create | — | REQUIRED | Auto-creates ancestor tags that don’t exist yet |
delete | REQUIRED | — | Cascades — deletes all descendants and removes all document assignments |
update | REQUIRED | — | Update color, description, or displayName |
Tag Hierarchy
Tags are organized as paths using/ separators. When you create /technology/ai/google, Moxn auto-creates /technology and /technology/ai if they don’t exist.
This hierarchy is used for:
- Organizing the tag catalog visually
- Backing database column options (select, multi-select, status, checkbox columns all reference tag IDs)
- Filtering in
findviatagIds