> ## Documentation Index
> Fetch the complete documentation index at: https://docs.attention.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Labels

> Manage label categories used to classify calls; apply or update labels on individual conversations.

Labels are the classification system Attention's AI uses to categorize calls (e.g. `Call Type` → `Discovery`, `Demo`, `Negotiation`). Each **label category** holds one or more **options**. Label categories can drive scorecard applicability, intelligence collection criteria, and reporting.

This group covers reading the catalog, managing categories and options (admin), and applying labels to individual conversations.

## Read tools

### list\_labels

> [!NOTE]
>
> Scope: `mcp:read`.

List label categories and their classification options. Each category contains options that Attention's AI uses to classify calls.

**team\_id** `string`

Filter labels by team ID. If omitted, returns all org labels.

**label** `string`

Search labels by name (case-insensitive substring match).

**ai\_flow** `boolean`

Filter by AI flow status. `true` = only AI-classified labels, `false` = only manual labels.

**Returns:** Markdown list of label categories with description, AI flow status, team scope, and options.

## Category write tools

### create\_label

> [!WARNING]
>
> Scope: `mcp:write`. Requires admin role.

Create a new label category. A label category contains one or more options that Attention's AI classifies calls into.

**label** `string` *required*

The name of the label category.

**description** `string`

Description of what this label represents.

**options** `array`

The classification options within this category. Each entry: `{ "value": "Pricing Discussion", "description": "Optional context for the AI" }`. A label category needs at least one option to classify calls.

**ai\_flow** `boolean`

Must be `true` for the label to appear in the UI and classify calls. Defaults to `true`.

**all\_teams** `boolean`

Apply to all teams. If `false`, use `team_ids`.

**team\_ids** `array`

Team IDs this label applies to. Ignored if `all_teams` is `true`.

***

### update\_label

> [!WARNING]
>
> Scope: `mcp:write`. Requires admin role.

Update an existing label category, including its classification options. Omitted fields preserve current values. Note that `options` is **replace-all** — providing it overwrites every existing option.

**label\_id** `string` *required*

The UUID of the label category.

**label** `string`

New name.

**description** `string`

New description. Set to empty string to clear.

**options** `array`

Replace the classification options for this category.

**ai\_flow** `boolean`

Whether this category is active in AI classification.

**all\_teams** `boolean`

Apply to all teams.

**team\_ids** `array`

Team IDs this label applies to.

***

### delete\_label

> [!WARNING]
>
> Scope: `mcp:write`. Requires admin role. Destructive.

Delete a label category and all its options. This is permanent.

**label\_id** `string` *required*

The UUID of the label category to delete.

## Conversation labels

### change\_conversation\_labels

> [!WARNING]
>
> Scope: `mcp:write`.

Apply or update labels on a specific conversation. Labels are passed as a key-value map where keys are label category names (use `list_labels` to see them).

**conversation\_id** `string` *required*

UUID of the conversation to label.

**labels** `object` *required*

Labels to set, as key-value pairs. Keys are label category names, values are the label values.

Example:

```json theme={null}
{ "Call Type": "Discovery", "Outcome": "Positive" }
```

**skip\_analysis** `boolean`

Skip CRM intelligence refresh after the label change. Default: `false`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.