Skip to main content
Glama

Make a launch video clip

launch_video
Read-onlyIdempotent

Use this when the user wants a short launch video for their own product page, such as "make a launch video from https://example.com/". Pass the page address. Returns a complete, self-contained HTML page with an animated CSS clip of about 12 seconds (name, headline, description, up to three headings, call to action), its scenes, and the source and as_of date. It reads the one public page, honouring robots.txt, copies no images and runs no scripts. It does not render a video file.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "https://a.example.com/"
    },
    "name": "launch_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAddress of your own product page, such as "https://example.com/". Only public websites are read.

Output Schema

NameRequiredDescriptionDefault
urlYes
htmlYesA complete, self-contained HTML page: inline CSS animation, no scripts, no external files.
sizeYes
as_ofYes
usageYes
noticeYes
scenesYes
sourceYes
statusYes
messageNo
final_urlYes
duration_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "url": "https://a.example.com/"
      +  }
      +]
  2. Changed1 schema field changed
    • removedOutput schema / properties / note_from_openkrill
      Removed value: -{
      -  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • addedOutput schema / properties / note_from_openkrill
      Added value: +{
      +  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive, and the description adds substantive context beyond that: it reads exactly one public page, honours robots.txt, copies no images, runs no scripts, and explicitly does not produce a video file. It also scopes the output consumption model (a complete, self-contained HTML page).

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?

Front-loaded with the trigger, then the input, then the return shape, then the constraints — a logical order with no filler. Slightly longer than needed; 'Pass the page address.' and parts of the output enumeration overlap with the schema and output schema.

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 one-parameter, read-only generation tool, everything an agent needs is present: when to call it, what to pass, what comes back, and the implicit limits (one page, no images, no scripts, no video file). The output schema exists, and the description still helpfully frames what the HTML contains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage and a single documented `url` parameter, the schema already carries the semantics. 'Pass the page address' and the ownership/public-site constraint largely restate what the schema says, adding only mild emphasis — the baseline 3 applies.

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?

States a specific verb and resource ('make a launch video') plus the concrete deliverable: a self-contained HTML page with a ~12 second animated CSS clip containing name, headline, description, up to three headings and a CTA. The closing line 'It does not render a video file' crisply distinguishes it from the video-output siblings like draft_video_script.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit trigger condition ('Use this when the user wants a short launch video for their own product page') with an example utterance, which is strong. It does not name or exclude any sibling tools (draft_video_script, make_cover, draft_tiktok_slides), so an agent comparing near-neighbours still has to infer the boundary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.