MCP tool

get_asset_status

Check an AI asset production job by id (from produce_asset). Jobs move submitting → queued → generating → ready, failed, or reconciliation-required. Poll while submitting/queued/generating; the other three states are terminal. Provider renders typically take tens of seconds to a few minutes (vo and programmatic motion complete synchronously at submit). When ready, outputUrl is the produced file (video/image/audio/animated SVG) ready to download or attach; sandbox mode (no provider keys) returns deterministic placeholder URLs. Failed means a definite provider failure: the wallet charge was refunded and retry creates a fresh debit. Reconciliation-required means provider acceptance is unknown: the charge is retained and retry is disabled to prevent duplicate production. Hand that state to a permitted human in Operator, then poll this tool; an MCP identity cannot assert the provider outcome.

Input

Pass fields from this schema as the tool arguments. Runtime ownership, product scope and readiness checks still apply.

Input JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "assetJobId": {
      "type": "string",
      "description": "asset job id, e.g. asset-1a2b3c4d"
    }
  },
  "required": [
    "assetJobId"
  ]
}

REST mapping and authority

The tool wraps this REST endpoint. The mapping identifies path/query/body transformations and approval or idempotency headers.

Request contract

{
  "method": "GET",
  "path": "/api/v1/assets/{assetJobId}",
  "pathFields": [
    "assetJobId"
  ],
  "pathSchema": {
    "type": "object",
    "properties": {
      "assetJobId": {
        "type": "string",
        "description": "asset job id, e.g. asset-1a2b3c4d"
      }
    },
    "additionalProperties": false,
    "required": [
      "assetJobId"
    ]
  },
  "pathEncoding": "encodeURIComponent for each path field",
  "governedAction": null,
  "headers": {},
  "querySchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "queryEncoding": "URLSearchParams; omit undefined fields, stringify supplied values",
  "responseMapping": "REST JSON is returned as MCP structuredContent and a compatibility text block; privacy-sensitive tools validate their output schema."
}

Output

This is the registered MCP output envelope. Nested fields are only modeled where the schema explicitly defines them.

Output JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "job": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    }
  },
  "required": [
    "job"
  ],
  "additionalProperties": {}
}

Safety annotations

MCP annotations

{
  "readOnlyHint": true,
  "destructiveHint": false,
  "idempotentHint": false,
  "openWorldHint": false
}

Annotations help a client present the tool. The API independently enforces authorization and exact action approvals. Error and retry guidance →