asset_update

Management

Update Asset

Update an asset's name, description, or tags. Args: - asset_id: required - metadata.name: optional new name - metadata.description: optional new description - metadata.tags: optional tag array — REPLACES the entire tag set. Use asset_add_tags / asset_remove_tags for diff-style changes against the existing tags. - team_id, project_id: required for OAuth callers Returns: the updated asset record, or { asset_id, tags } when only tags were changed. Example: "Rename this asset" -> asset_id="asset_xxx", metadata={"name": "new-name"}

open-world

Parameters

Name	Type	Required	Description
asset_id	string	✓	Asset ID.
metadata	unknown	—	Asset metadata for update (name, description, tags).
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

JSON

{
  "asset_id": "asset_img001",
  "metadata": {
    "name": "Dragon at Sunset",
    "tags": [
      "dragon",
      "fantasy",
      "sunset"
    ]
  },
  "team_id": "team_abc123",
  "project_id": "proj_xyz789"
}

Example Response

JSON

{
  "asset": {
    "id": "asset_img001",
    "name": "Dragon at Sunset"
  }
}

Common Use Cases

Update asset name and tags for better organization and searchability
Rename assets after a batch generation run