What it does
Create a tag. color is one of: violet, red, emerald, amber, blue, pink, teal, slate. Tags belong to one workspace and can only be attached to tasks on that board, so pass workspace_id (from list_workspaces, or a task's own) when the tag is for a workspace other than the personal one — a tag made in the wrong workspace can't be attached and has to be deleted and remade.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
name | string | Required |
|
color | string | Optional |
|
workspace_id | string | Optional | Which workspace the tag belongs to. Optional — omitted, it lands in this account's personal workspace. Must be a workspace this account is a member of; ids come from list_workspaces. |
idempotency_key | string | Optional | Optional. One key per operation: pass the same key only when retrying this exact call, so a retry after a timeout replays the first result (a key already used on a different tool is refused, and keys expire after 48 hours) instead of creating a duplicate tag. |
Annotations
The hints the server sends with this tool. A host reads them to decide whether to ask you before a call.
- Read-only
readOnlyHint: false - Changes data in your Done account.
- Destructive
destructiveHint: false - Only adds or reads; nothing already there is removed or overwritten.
- Idempotent
idempotentHint: false - Each call can add something new, such as a comment, a run or a task.
- Open world
openWorldHint: false - Touches only your own Done account.
Which tokens can call it
A connection made with OAuth has full access. A token from Settings → Agent access → Extra MCP tokens can be narrowed, and a narrowed token never sees beyond its project or workspace.
- Full accessAllowed
- Read-only tokenRefused
- Single-project tokenRefused
- Single-workspace tokenAllowed
Try it
With Done connected, ask your assistant something like:
“Create a tag called quick-win.”
Connect Done to your assistant
One MCP endpoint per account, over OAuth or a token. Step-by-step setup for each client: