# stensul-list-gallery-images

> Browses the account's approved image gallery. Use it before asking the user for a file.

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

- Scope: `dam:read`
- Access: read

`name` is a substring match on the image name, not a search of what the picture shows. Browse without it when unsure.

## Inputs

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | no | Part of the image name, case-insensitive. |
| `page_number` | integer ≥ 1 | no | Page number (default 1). |
| `page_size` | integer 1–30 | no | Results per page (max 30, default 10). |
| `sort` | "createdAt" \| "-createdAt" \| "updatedAt" \| "-updatedAt" | no | Default `-createdAt` (newest first). |

## Example request

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "stensul-list-gallery-images",
    "arguments": {
      "name": "autumn",
      "page_size": 10
    }
  }
}
```

## Response

Gallery images with their `url`, which you can pass as `imageContent.source_url` in `stensul-build-email`.

## 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. |