Wait for an asset
wait_for_assetWait until assets are usable, then return each one's placement lines. Takes up to 20 Asset IDs per call (assetIds), so split a longer list over several calls: imports, generations, your own uploads, and uploads the user started, which search_assets lists with preparing set while they upload or encode. Every upload is analyzed after it encodes (usually under 15 seconds): an asset still analyzing can be seen but not placed, and this waits for that too. A ready asset comes with its brief: what happens, what is on screen and heard, the moments to use or cut, the lines to quote, and the problems; read_asset has the whole brief. Answers when all of them are ready or failed, each with its reason (a plan limit says so). One call waits at most 50 seconds (waitSeconds, null for the longest wait); if some are still processing or analyzing then, it names them with their progress: start on the ready ones, tell the user, and call wait_for_asset again with those ids. skipAnalysis true lets the assets through without waiting for their analysis. Use this after an import or upload, and whenever an asset is still uploading, processing or analyzing, before placing or analyzing it.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| assetIds | Yes | Every Asset ID to wait for, in one call: all the uploads, imports or generations the next step needs. 1 to 20. | |
| projectId | Yes | The project this call runs on without changing the open project. null (or leaving it out) uses the open project. wait_for_jobs takes the projectId of the calls that started the jobs. | |
| waitSeconds | Yes | Seconds to wait for the assets to become usable before answering, 0 to 50. null waits 50. | |
| skipAnalysis | Yes | true: use the assets now, without waiting for their analysis (transcript, shots, sound, brief); it keeps running and read_asset shows it later. Only when the user wants the asset used at once. null or false waits for the analysis. |