assets_list

Management

List Assets

List assets in the current project with heavy fields stripped. Args: - filters: optional — model_id, tags, type (single), or types (array). Use filters.types for multiple types in one call. Common groups: 3D = ["uploaded-3d", "img23d", "txt23d", "3d23d"], images = ["txt2img", "img2img", "uploaded"], video = ["img2video", "txt2video", "uploaded-video"], audio = ["txt2audio", "audio2audio", "uploaded-audio"]. - limit: results per page (default 20, max 100) - page_token: pagination token from a previous response (nextPaginationToken) - team_id, project_id: required for OAuth callers Returns: { assets } array (heavy fields stripped — embedding, properties, editCapabilities, thumbnail, firstFrame, lastFrame, preview) plus nextPaginationToken when more pages exist. Avoid embedding CDN URLs when listing assets — oversized responses consume tokens and slow display. Don't use when: you want to SHOW an asset — use asset_display.
read-onlyidempotentopen-world

Parameters

NameTypeRequiredDescription
filtersunknownFilters for list action. Use types (array) to query multiple types at once.
limitnumber20Results per page.
page_tokenstringPagination token from previous response.
team_idstringTeam ID. Required if user belongs to multiple teams.
project_idstringProject ID to scope the operation to.
response_formatenum(json | markdown)jsonOutput format: 'json' for structured data, 'markdown' for human-readable text.

Example Request

JSON
{
  "filters": {
    "type": "image"
  },
  "limit": 20,
  "team_id": "team_abc123",
  "project_id": "proj_xyz789"
}

Example Response

JSON
{
  "assets": [
    {
      "id": "asset_img001",
      "name": "dragon_sunset.png",
      "mimeType": "image/png",
      "createdAt": "2026-03-20T10:00:00Z"
    }
  ],
  "nextPageToken": "tok_page2"
}

Common Use Cases

  • List all generated images in a project to review recent outputs
  • Page through assets with nextPageToken for large libraries