Launch film from a website
make_launch_filmTurns a product website or app listing into a 20–40 second launch film, rendering an MP4 with music and sound effects from the page’s own brand and content.
Instructions
Use it when the user wants a launch video, product video, promo, teaser or announcement clip for a product's site or app. Makes a 20 to 40 second launch film from a product's own site in one job: it reads the brand and the page, plans the film (name and promise, the real screen in a browser window, the page's own headline, feature cards, a number the page states when it finds one, the logo close) and renders film.mp4 with music and sound effects, with Chrome and ffmpeg on this machine. Nothing is generated by AI: the film shows what the site says. The result shows film.json, the plan, next to words.json, the page's words, and frames/sheet.jpg has two stills a clip. The film is 25 frames a second at 1920x1080 or 1080x1920, its sound about -14 LUFS. Its music is the look's own, or a track of the user's that film.json names. For the user's own track, plan with music false and give the rendered film to fit_music as video. For a plan to read or change before it renders, use plan_launch_film instead. The address needs a dot in its host name, so localhost on its own is refused. The launch-film 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": {
"url": "<url>"
},
"name": "make_launch_film"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sfx | No | Set to false to leave out the sound effects. | |
| url | Yes | The product's website, like https://linear.app, or its App Store or Google Play listing. A social profile is refused, and so is a host without a dot, like localhost. | |
| jobs | No | Clips rendered at once (default 2). 1 suits a slow machine. | |
| keep | No | Keep the work files, each clip's MP4, in a launch-film-work- folder in the system's temp folder, outside the film's folder; the summary names it. | |
| look | No | The film's look, which also sets the tempo of its music and so how long a bar lasts (default: picked from the brand). launch_film_guide with topic looks says what each one suits. | |
| brand | No | A brand kit you already have: its folder or its brand.json. make_brand_kit makes one. The kit copies the kit given into brand/ in the film's folder; without one, it reads the brand from the site itself. | |
| music | No | Set to false to leave out the look's music bed, as when the user's own track goes under the film later. | |
| words | No | A words.json from an earlier plan or film, used instead of reading the page again, so a second aspect keeps the same words. | |
| aspect | No | 16:9 (default) or 9:16 for phones. For both, make the second one with words from the first. | |
| out_dir | No | Folder to save into, absolute or relative to /app. Default: launch-film-<host>, where <host> is the site's host without www or the port. A run replaces the files an earlier run of this kit left there, so give each version its own out_dir. The kit deletes the brand/ folder in it and makes it again when given brand, or for an App Store page, so it does not start then while that folder holds a file other than a kit's own that would be lost. Otherwise it makes the kit in brand/ again where it is, so it does not start while brand/ holds a file named like a kit's own, in any letter case, that its brand.json does not list. To use that brand/ folder where it is, give brand as out_dir with /brand added, written the same way. | |
| seconds | No | Aim for this length (default 30). Clips last whole bars of the look's music and the plan never stretches one to fill the time, so the film can end several seconds away from it, often short; film.timeline.json has its exact length. | |
| 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 |