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



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

Attach a label to a work item (by id or name; create-on-capture).

|                     |                      |
| ------------------- | -------------------- |
| Required permission | `work:write`         |
| Capability ID       | `workItems.addLabel` |
| Destructive         | No                   |

## Parameters [#parameters]

| Parameter | Type          | Required | Notes |
| --------- | ------------- | -------- | ----- |
| `id`      | string (uuid) | yes      |       |
| `labelId` | string (uuid) | no       |       |
| `name`    | string        | no       |       |

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

```json
{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "format": "uuid"
    },
    "labelId": {
      "type": "string",
      "format": "uuid"
    },
    "name": {
      "type": "string",
      "minLength": 1,
      "maxLength": 60
    }
  },
  "required": [
    "id"
  ],
  "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.