Vidova

Wait for an asset

wait_for_asset

Read-onlyIdempotent

Wait until assets are placeable, then return each one's placement lines: its source facts (width, height, fps, duration, hasAudio), what fit="cover" does to it in the film, a READY line and the use line. Takes every Asset ID the next step needs in one call, up to 200 (assetIds): imports, generations, your own uploads, uploads the user started, which search_assets lists with preparing set while they upload or encode, and Library ids of files still uploading (search_library, add_from_library): it adds each to the project once its upload lands and answers its Asset ID, which you use from then on. A call of more than 20 ids names where each one stands in a line: search_assets lists their facts. 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 then, it names them with their progress and a NEXT line: start on the ready ones, tell the user, and call wait_for_asset again with those ids. Nothing reads what a file shows or says on its own: read_asset draws its picture, and transcribe_asset, detect_scenes, detect_beats and search_video_moments read its content when the edit needs it. Use this after an import or upload, and whenever an answer says NOT PLACEABLE YET, before placing or analyzing the asset.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "assetIds": "<assetIds>",
      "waitSeconds": "<waitSeconds>",
      "projectId": "<projectId>"
    },
    "name": "wait_for_asset"
  }
}

Input Schema

Name	Required	Description
`assetIds`	Yes	Every Asset ID to wait for, in one call: all the uploads, imports or generations the next step needs. 1 to 200.
`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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 30, 2026

removedInput schema / properties / skipAnalysis

Removed value: -{
-  "anyOf": [
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "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."
-}

changedInput schema / required

Previous value: -[
-  "assetIds",
-  "waitSeconds",
-  "skipAnalysis",
-  "projectId"
-]New value: +[
+  "assetIds",
+  "waitSeconds",
+  "projectId"
+]

Changed2 schema fields changedOct 20, 2026

changedInput schema / properties / assetIds / description

Previous value: -"Every Asset ID to wait for, in one call: all the uploads, imports or generations the next step needs. 1 to 20."New value: +"Every Asset ID to wait for, in one call: all the uploads, imports or generations the next step needs. 1 to 200."

changedInput schema / properties / assetIds / maxItems
```
Previous value: -20New value: +200
```

First observedOct 19, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial behavior beyond them: the 50-second cap per call, what a timeout response contains (progress plus a NEXT line), what a >20-id call returns, that failures come back with a reason including plan limits, and that library ids are auto-added to the project. That is exactly the operational detail annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and trigger are front-loaded, and most sentences carry needed information. However, the prose is a set of long run-on sentences, and the clause 'A call of more than 20 ids names where each one stands in a line: search_assets lists their facts' is ambiguous enough to cost comprehension. It could be tightened without losing substance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description fully carries the return contract: source facts (width, height, fps, duration, hasAudio), cover-fit behavior, READY line, use line, per-asset failure reasons, and the partial-result shape. For a polling tool with three required params, nothing an agent needs to call or re-call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: assetIds should carry every id the next step needs in one call (batching rationale, up to 200), and waitSeconds=null means the longest wait rather than 'no wait'. It also clarifies the retry pattern of re-calling with the still-pending ids. Minor loss: projectId's behavior is left almost entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening states a specific verb and resource with its scope: 'Wait until assets are placeable, then return each one's placement lines.' It also enumerates the asset kinds it accepts (imports, generations, uploads, in-progress library uploads) and explicitly separates itself from content readers (read_asset, transcribe_asset, detect_scenes). An agent can pick it out of the ~80 siblings without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit trigger conditions are given ('after an import or upload, and whenever an answer says NOT PLACEABLE YET, before placing or analyzing the asset') along with the retry protocol (start on ready ones, tell the user, call again with remaining ids). Alternatives are named with their distinct jobs: search_assets for facts, read_asset/transcribe_asset/detect_scenes/detect_beats/search_video_moments for content.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Vidova tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.