Skip to main content
Glama

Demo video of a website

record_demo_video
Destructive

Record 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

NameRequiredDescriptionDefault
fpsNoFrames a second (default 30); steps.json counts its frames at this rate.
gifNoSet to false to skip demo.gif, which is made smaller until it is 8 MB at most.
urlYesThe 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.
hideNoCSS selectors of more elements to hide, on top of any under hide in steps.
langNoThe site's version in this language, when it has one: a language code like de or pt-BR.
pageNoPages 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.
zoomNoHow 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.
cleanNoSet 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.
frameNoSet to false for the page alone, filling the video, without the window and the backdrop.
pagesNoPages 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.
stepsNoA 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.
themeNoThe site's light or dark look (default light).
out_dirNoFolder 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.
backgroundNoBehind 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_secondsNoHow 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_motionNoAsk the site for its reduced-motion version.
timeout_secondsNoGive 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

NameRequiredDescriptionDefault
kitYes
docsNoThe notes the text shows, and where each one is.
nextNoWhat to do next, as the Next line says.
toolYes
filesNo
folderNoWhere the kit saved its files.
job_idYes
passedNoFor checks: whether the check passed.
statusYes
continuedNoTrue when this call continued the job of an identical call whose answer did not reach the client, instead of starting another.
exit_codeNo
last_lineNoWhat the kit was doing last.
expires_atNoWhen the download links stop working.
next_actionNo
elapsed_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed22 schema fields changedv0.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / background / description
      Previous value: -"Behind the window: a colour like #0f172a, two or three colours for a gradient, or a picture file."New value: +"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."
    • changedInput schema / properties / clean / description
      Previous value: -"Set to false to keep the banners and bubbles."New value: +"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."
    • changedInput schema / properties / fps / description
      Previous value: -"Frames a second (default 30)."New value: +"Frames a second (default 30); steps.json counts its frames at this rate."
    • changedInput schema / properties / frame / description
      Previous value: -"Set to false for the page alone, filling the video."New value: +"Set to false for the page alone, filling the video, without the window and the backdrop."
    • changedInput schema / properties / gif / description
      Previous value: -"Set to false to skip demo.gif."New value: +"Set to false to skip demo.gif, which is made smaller until it is 8 MB at most."
    • changedInput schema / properties / hide / description
      Previous value: -"CSS selectors of more elements to hide."New value: +"CSS selectors of more elements to hide, on top of any under hide in steps."
    • addedInput schema / properties / lang / anyOf
      Added value: +[
      +  {
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  }
      +]
    • changedInput schema / properties / lang / description
      Previous value: -"The site's version in this language, when it has one."New value: +"The site's version in this language, when it has one: a language code like de or pt-BR."
    • removedInput schema / properties / lang / minLength
      Removed value: -1
    • removedInput schema / properties / lang / type
      Removed value: -"string"
    • changedInput schema / properties / out_dir / description
      Previous value: -"Folder to save into, absolute or relative to /app. Default: easyscreenshotkit-demo-{host}."New value: +"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."
    • changedInput schema / properties / page / description
      Previous value: -"Pages to take in the tour, like /pricing."New value: +"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."
    • changedInput schema / properties / pages / description
      Previous value: -"Pages in the tour, the home page included (default 4)."New value: +"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."
    • changedInput schema / properties / steps / description
      Previous value: -"A YAML or JSON file of steps to follow instead of a tour: visit, scroll, click, type, wait, hover, key."New value: +"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."
    • changedInput schema / properties / timeout_seconds / description
      Previous value: -"Give up after this many seconds (default 900)."New value: +"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."
    • changedInput schema / properties / url / description
      Previous value: -"The website, like https://linear.app"New value: +"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."
    • changedInput schema / properties / wait_seconds / description
      Previous value: -"How long to wait for the result before returning a job_id to wait on. 45 is safe for clients that stop a tool call after 60 seconds."New value: +"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."
    • changedInput schema / properties / zoom / description
      Previous value: -"How far a click zooms in, 1 to 2.5 (default 1.5). 1 means no zoom."New value: +"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."
    • addedOutput schema / properties / continued
      Added value: +{
      +  "description": "True when this call continued the job of an identical call whose answer did not reach the client, instead of starting another.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / docs
      Added value: +{
      +  "description": "The notes the text shows, and where each one is.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "name": {
      +        "type": "string"
      +      },
      +      "path": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / next
      Added value: +{
      +  "description": "What to do next, as the Next line says.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (destructive/openWorld/non-idempotent), the description discloses distinctive behavior: a job_id is returned after wait_seconds so the call is asynchronous, out_dir is replaced only on success and left intact on failure/cancel and must be empty or a prior run, and timeout_seconds determines how many tour pages get captured. These are non-obvious operational traits an agent needs and none are in the annotations.

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

Conciseness4/5

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

Triggers and core behavior are front-loaded, then outputs, then parameter notes. It is dense and occasionally run-on (the steps.json clause stacks several ideas), but nearly every sentence carries actionable content; the playbook pointer earns its place.

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?

For a 17-parameter, asynchronous, file-writing tool, the description covers async job handling, output artifacts, out_dir safety, timeout effects, and the tour-vs-steps distinction. With an output schema present, it need not explain return values, and nothing an agent needs to call it correctly appears 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 schema already carries per-parameter meaning. The description still adds cross-parameter semantics the schema cannot: steps targets are CSS selectors or text=<words>, pages/page apply to tours only, and a page takes roughly 4-8 seconds. Some parameters (fps, gif, lang) get no extra prose, keeping it below 5.

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?

"Records a short demo video of a website" gives a specific verb and resource, and the description immediately scopes it (tour of pages, or steps in a file) and names the sibling it is not (take_screenshots). An agent can distinguish it from take_screenshots and the video siblings without opening any 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?

The opening sentence enumerates the trigger conditions (demo video, walkthrough, GIF, footage of the real site for a video) and explicitly routes still-image needs to take_screenshots. It also points to makersmcp_playbook for the fuller workflow, giving a clear when and a clear alternative.

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