Demo video of a website
record_demo_videoRecord a short website demo video or GIF using page tours or scripted steps, with a visible pointer, click zooms, and saved MP4, GIF, poster, and timing data.
Instructions
Use it when the user wants a demo video, a walkthrough, a GIF of a site, or footage of the real site for a video. Records a short demo video of a website: a tour of the pages worth showing, or the steps in a file. The page plays in a browser window on a backdrop, with a visible pointer, smooth scrolling and a zoom on each click; cookie banners and chat bubbles are hidden, never clicked. Saves demo.mp4 (1920x1080, H.264, no sound), demo.gif, poster.png, the picture to show first, and steps.json: each step's start and end, and each click's moment as pressedAt, which music and captions are timed from. A steps file's targets are CSS selectors or text=, and pages and page are for a tour only. A tour gives a page about 4 to 8 seconds. For still screenshots, use take_screenshots instead. The demo-video playbook (makersmcp_playbook) has the whole job. (easyscreenshotkit 0.1.3, 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": "record_demo_video"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fps | No | Frames a second (default 30); steps.json counts its frames at this rate. | |
| gif | No | Set to false to skip demo.gif, which is made smaller until it is 8 MB at most. | |
| url | Yes | The website, like https://linear.app. It replaces a steps file's url line and starts a file whose first step is no visit; a visit to a whole address, as every visit in a tour's demo.yaml, still opens that address. | |
| hide | No | CSS selectors of more elements to hide, on top of any under hide in steps. | |
| lang | No | The site's version in this language, when it has one: a language code like de or pt-BR. | |
| page | No | Pages of the same site to take in the tour, like /pricing, or views of a web app by their #route, like /app/#/plants, each taken even past pages. For a tour only. | |
| zoom | No | How far a click zooms in, 1 to 2.5 (default 1.5). 1 means no zoom. A step in a steps file can set its own. | |
| clean | No | Set to false to keep the banners and bubbles; hide still hides what it names. Otherwise everything fixed on the screen is hidden but a bar along its top and one down a side, so a step that clicks in an app's bottom tab bar needs this false. | |
| frame | No | Set to false for the page alone, filling the video, without the window and the backdrop. | |
| pages | No | Pages in the tour, the home page included (default 4). A page that scrolls takes about 4 to 8 seconds and one that fits on the screen about 2. The tour starts at the site's root and puts pricing last. For a tour only. | |
| steps | No | A YAML or JSON file of steps to follow instead of a tour, one action a step: visit, scroll, click, type, key, hover or wait. A target is a CSS selector or text=<words>, and a selector that starts with # goes in quotes. demo.yaml from an earlier tour is one to start from. Not with pages or page. | |
| theme | No | The site's light or dark look (default light). | |
| out_dir | No | Folder to save into, absolute or relative to /app. Default: easyscreenshotkit-demo-<host>, where <host> is the site's host without www or the port. A run replaces what an earlier run of this tool left there once it has ended well, and one that fails or is canceled leaves it as it was: give each version its own out_dir. The folder must be empty or hold an earlier run of this tool: any other folder stops it. | |
| background | No | Behind the window, by default a gradient, dark behind a light site and light behind a dark one: a colour like #0f172a, two or three colours for a gradient, or a .png, .jpg, .jpeg, .webp, .gif, .avif or .svg picture file. | |
| 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. | |
| reduced_motion | No | Ask the site for its reduced-motion version. | |
| timeout_seconds | No | Give up after this many seconds (default 900). A tour looks for more pages only while more than 240 seconds are left, so a short one records the home page, url and each page alone, and a step starts while 60 seconds are left, or a quarter of a shorter run's time. |
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 |