# stensul-list-segment-sets

> Lists the Segment Sets available for a library: each set's name, segment type and ordered segments.

Source: https://stensul.com/developers/reference/stensul-list-segment-sets/ · From the live server's tool list, 2026-09-28

- Scope: `dynamic-content:read`
- Access: read

Check `dca_segment_sets.supported` in `stensul-get-libraries` first. Not every library supports Segment Sets.

## Inputs

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `libraryId` | string | yes | Library ID. |

## Example request

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "stensul-list-segment-sets",
    "arguments": {
      "libraryId": "64f0c0ffee0000000000beef"
    }
  }
}
```

## Response

Segment Sets with their segments in order.

## Errors

| Status | Message | Cause | Fix |
| --- | --- | --- | --- |
| 401 | Authentication expired or missing | The session's authorization expired. | Sign in again when the host prompts. On a 401 or 403, the server's instructions tell the model to re-check sign-in first. |
| 403 | Insufficient OAuth scope (403): The token lacks the required scope | The API connection doesn't have the scope this tool needs. | An admin adds the scope to the API connection. Then sign in again: adding a scope revokes existing tokens. |
| 403 | API error (403): Action is unauthorized. | The signed-in user's role lacks the permission, for example `edit_campaign`. | Grant the permission to the user's role in Admin > Users & Roles. It works for other users on the same connection. |