asset_update
ManagementcatalogUpdate Asset
Not in the default tool list
This tool lives in the tool catalog. Discover it with scenario_tools_search (or enumerate everything with scenario_tools_list) and run it via scenario_tool_execute_write. To list every tool directly, connect with ?toolsets=full.
Update an asset's name, description, or tags. Provided values replace the previous values; setting tags can remove existing tags. Confirm the target and replacement first.
Args:
- asset_id: required
- metadata.name: optional new name
- metadata.description: optional new description. Also sets a training image's caption, since training image ids are asset ids (image training; needs write access to the asset). Read captions in model_get's trainingImages (catalog-only — run via scenario_tool_execute_read) or with asset_get; automaticCaptioning is the fallback used when no description is set. Never write an empty description on a training image: it hides the auto-caption, and train action="start" then fails with a missing-caption error. Audio assets differ: a caption stored in their properties.description takes precedence, and asset_update does not write it.
- 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"}
destructiveopen-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 with project_id for OAuth callers; an API key is scoped by the key. |
| project_id | string | — | Project ID. Required with team_id for OAuth callers; an API key is scoped by the key. |
| 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