display_asset

Display

Display Asset

Display a Scenario asset inline. ALWAYS use this tool to show images, videos, audio, and 3D models to the user instead of pasting raw asset URLs. Pass the asset_id returned by run_model or other asset-producing tools. Args: - asset_id: required — asset to display - format: 'display' (default), 'viewer', 'json', or 'markdown' - team_id, project_id: required for OAuth callers Returns: display returns inline image content for images plus viewer structuredContent; viewer returns a lightweight response for MCP App-capable hosts; json and markdown return metadata and links. If the host renders the interactive widget, do not restate the visual in text — just provide the app_url link. Examples: - "Display this asset_xxx" -> asset_id="asset_xxx" - "Show the result of run_model" -> asset_id="asset_xxx" - "Render only the interactive viewer" -> asset_id="asset_xxx", format="viewer" Don't use when: You need to edit metadata, tags, or other asset records, or when you were about to call manage_assets get just to show the asset. Prefer manage_assets for CRUD and display_asset for rendering.

read-onlyidempotentopen-world

Parameters

NameTypeRequiredDescription
asset_idstringThe asset ID to display (e.g. 'asset_xxx'). Can display images, videos, audio, and 3D models.
formatenum(display | json | markdown | viewer)displayOutput format. 'display': inline image + clickable links (default, best for showing to user). 'viewer': lightweight response for MCP App-capable hosts (no inline image, viewer renders the visual). 'json': structured metadata. 'markdown': human-readable text with links.
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
{
  "asset_id": "asset_img001",
  "format": "display",
  "team_id": "team_abc123",
  "project_id": "proj_xyz789"
}

Example Response

JSON
{
  "asset_id": "asset_img001",
  "mimeType": "image/png",
  "download_url": "https://cdn.scenario.com/assets/asset_img001.png?token=...",
  "app_url": "https://app.scenario.com/assets/asset_img001"
}

Common Use Cases

  • Show generated images inline in the chat after a run_model call
  • Retrieve a download URL to save a generated asset locally
  • Display video or 3D asset links when inline rendering is not supported
  • Get structured JSON metadata about an asset for programmatic use