Check a video scene
video_checkChecks a scene document with the engine's strict reader without rendering it: ok, or one sentence naming the first problem and the key it is at, with every other problem in the scene listed in result.errors (up to fifty), so one call finds them all. A scene with dialogue is spoken while it is read, so a long one takes a few seconds, and a line that overlaps the same character's last, or ends after the scene, is named. Costs no units.
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": {
"scene": "<scene>"
},
"name": "video_check"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| scene | Yes | A scene document written inline: output (size, frame rate, length), tracks of clips, optional cast and lines, audio and subtitles. Start from video_examples and read video_schema for every key. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ms | No | Milliseconds the run took. | |
| job | Yes | The job id; the job tool reads it. | |
| verb | No | The tool that made it. | |
| files | No | Files made, each with a name, type, size and a signed URL. | |
| units | No | Units this call cost. | |
| result | No | The engine's own answer, a JSON document. | |
| status | No | queued when the job runs in the background. |