# create_label (/docs/reference/mcp-tools/create_label)



{/* Generated by apps/docs/scripts/generate-mcp-pages.mjs — do not edit by hand. */}

Create a workspace label.

|                     |                 |
| ------------------- | --------------- |
| Required permission | `work:write`    |
| Capability ID       | `labels.create` |
| Destructive         | No              |

## Parameters [#parameters]

| Parameter | Type   | Required | Notes |
| --------- | ------ | -------- | ----- |
| `name`    | string | yes      |       |
| `color`   | string | no       |       |

## Input schema (JSON Schema) [#input-schema-json-schema]

```json
{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "maxLength": 60
    },
    "color": {
      "type": "string",
      "minLength": 1,
      "maxLength": 32
    }
  },
  "required": [
    "name"
  ],
  "additionalProperties": false
}
```

## Access control [#access-control]

A call succeeds only when the personal access token's scopes **and** the holder's role both allow `work:write` (effective permission = scope ∩ role, default-deny). The tool runs inside the token owner's organization — tenancy is never a parameter.