manage_assets
ManagementManage Assets
CRUD for assets. Actions: list, get, update, copy, download, delete, get_bulk. Tag management: list_tags, add_tags, remove_tags. Args: - action: required operation (see above) - asset_id: required for get, update, copy, download, add_tags, remove_tags - asset_ids: required for delete, get_bulk - filters: optional for list — model_id, tags, type (single), or types (array for multiple types in one call) - response_format: 'json' (default) or 'markdown' Returns: asset metadata (JSON or markdown). list returns paginated array — use page_token for next page. Avoid embedding CDN URLs when listing assets, it produces oversized responses consuming a lot of tokens and makes the list display slow. Prefer display_asset for viewing an asset. Calling display_asset will render the asset (images, video, audio and 3D) directly for the user. Examples: - "Show me my latest 10 assets" -> action="list", limit=10 - "Show the next page" -> action="list", limit=10, page_token="<token from previous response>" - "List my 3D files" -> action="list", filters={"types": ["uploaded-3d", "img23d", "txt23d", "3d23d"]} - "List my images" -> action="list", filters={"types": ["txt2img", "uploaded"]} - "Get details on these assets" -> action="get_bulk", asset_ids=["id1", "id2"] - "Rename this asset" -> action="update", asset_id="...", metadata={"name": "new-name"} Don't use when: You want to show an asset to the user. Prefer display_asset for rendering.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| action | enum(list | get | update | copy | download | delete | get_bulk | list_tags | add_tags | remove_tags) | ✓ | Asset action: list, get, update, copy, download, delete, get_bulk, list_tags, add_tags, or remove_tags. |
| asset_id | string | — | Asset ID (required for get/update/copy/download). |
| asset_ids | array | — | Asset IDs (required for delete/get_bulk). |
| metadata | unknown | — | Asset metadata for update, or format for download. |
| filters | unknown | — | Filters for list action. Use types (array) to query multiple types at once. |
| tags | array | — | Tags to add or remove (for add_tags/remove_tags actions). |
| limit | number | 20 | Results per page. |
| page_token | string | — | Pagination token from previous response. |
| team_id | string | — | Team ID. Required if user belongs to multiple teams. |
| project_id | string | — | Project ID to scope the operation to. |
| response_format | enum(json | markdown) | json | Output format: 'json' for structured data, 'markdown' for human-readable text. |
Example Request
{
"action": "list",
"filters": {
"type": "image"
},
"limit": 20,
"team_id": "team_abc123",
"project_id": "proj_xyz789"
}Example Response
{
"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
- Update asset tags and names for better organization and searchability
- Bulk-fetch multiple assets by ID after a batch generation run
- Delete outdated or unwanted assets to keep the project clean