Check a video
check_videoVerifies a video before publishing by measuring size, frame rate, length, loudness, silence, blank or frozen stretches, and beat-aligned cuts with ffmpeg, then reports pass/fail checks.
Instructions
Use it when the user wants a video checked before it goes out: size, frame rate, length, loudness, blank or frozen stretches, cuts on the beat. Checks any video by measuring it with ffmpeg: size, frame rate, length, black, still and silent stretches, loudness, true peak, clipping, and whether the cuts land on the beat. It writes CHECK.md (pass or fail, with every check), which the result shows, check.json, sheet.png (a frame from each shot) and wave.png (the sound over time). A failed check is a normal result here. It knows no platform, and does not measure file size, codec, bitrate or the space an app's buttons cover. For a place's limits, file size and codecs, use check_place_limits instead. A launch film is 25 frames a second and measures about -14 LUFS as it was rendered. The checks playbook (makersmcp_playbook) has the whole job. (launch-film 0.3.1, on this machine.)
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": {
"film": "<film>"
},
"name": "check_video"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cues | No | The cues.json of the music under the video, to check the cuts land on the beat. analyze_music writes one for a track played as it is. fit_music writes one for a fitted track. A track with no steady beat gives empty beats, which this refuses. | |
| cuts | No | The cuts in seconds, like 3.2,7.5, or a JSON file of seconds, of frames with their fps, or a launch-film timeline, when no timeline of the video's own name is next to it: a renamed or mixed copy of a launch film takes its film.timeline.json here. A demo's steps.json is not one: give its clicks' pressedAt as seconds. | |
| film | Yes | The video to check, like film.mp4. A launch-film timeline next to it under the same name, like film.timeline.json next to film.mp4, gives the cuts. | |
| lufs | No | The integrated loudness it should have, like -14, give or take 1 LU. A launch film is rendered to about -14, the level YouTube, X and most social apps play at, so give a value only when the user needs another. | |
| allow | No | Stretches meant to hold still, black or silent, in seconds, like 27-30,0-0.5. | |
| expect | No | The size and frame rate it should have, as WxH@fps, WxH or @fps: 1920x1080@25 for a launch film (1080x1920@25 for 9:16), and for a demo its size at the fps it was recorded with. | |
| out_dir | No | Folder to save into, absolute or relative to /app. Default: <film-folder>/check, where <film-folder> is the folder film is in. | |
| seconds | No | The length it should have: 30 is give or take 0.5 seconds, and a range like 28-32 takes anything inside it. A launch film's exact length is seconds in its film.timeline.json. | |
| wait_seconds | No | How long to wait for the result, counted from the start of the call, before returning a job_id to wait on. Some clients end a call after 60 or 240 seconds; 45 is safe in all of them. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kit | Yes | ||
| docs | No | The notes the text shows, and where each one is. | |
| next | No | What to do next, as the Next line says. | |
| tool | Yes | ||
| files | No | ||
| folder | No | Where the kit saved its files. | |
| job_id | Yes | ||
| passed | No | For checks: whether the check passed. | |
| status | Yes | ||
| continued | No | True when this call continued the job of an identical call whose answer did not reach the client, instead of starting another. | |
| exit_code | No | ||
| last_line | No | What the kit was doing last. | |
| expires_at | No | When the download links stop working. | |
| next_action | No | ||
| elapsed_seconds | Yes |