Skip to main content
Glama

Plan a launch film

plan_launch_film
Destructive

Plan a launch film's look, length and words from a product page before rendering, so you can review and edit film.json, its script and brand notes first.

Instructions

Use it when the user wants to choose a launch film's look, length or words, or to read its plan before it renders. Reads a product's brand and page and writes film.json, the plan of a launch film, without rendering it. The result shows film.json, words.json (the page's words) and brand/BRAND.md, so every word on screen can be checked against the page before the render. Change film.json where it is wrong (launch_film_guide with topic types lists the scene types), then render it with render_launch_film. A second aspect is a second plan with words from the first and the other aspect. For a film in one job, use make_launch_film instead. 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": "plan_launch_film"
  }
}

Input Schema

NameRequiredDescriptionDefault
sfxNoSet to false to plan the film without sound effects.
urlYesThe 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.
lookNoThe 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.
brandNoA 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.
musicNoSet to false to plan the film without the music bed, as when the user's own track goes under it later.
wordsNoA words.json from an earlier plan or film, used instead of reading the page again, so a second aspect keeps the same words.
aspectNo16:9 (default) or 9:16 for phones. For both, plan the second one with words from the first.
out_dirNoFolder 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.
secondsNoAim 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.
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.

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. Changed13 schema fields changedv0.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / aspect / description
      Previous value: -"16:9 (default) or 9:16 for phones."New value: +"16:9 (default) or 9:16 for phones. For both, plan the second one with words from the first."
    • changedInput schema / properties / brand / description
      Previous value: -"A brand kit you already have: an easybrandkit folder or its brand.json."New value: +"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."
    • changedInput schema / properties / look / description
      Previous value: -"The film's look (default: picked from the brand)."New value: +"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."
    • changedInput schema / properties / music / description
      Previous value: -"Set to false to plan the film without the music bed."New value: +"Set to false to plan the film without the music bed, as when the user's own track goes under it later."
    • changedInput schema / properties / out_dir / description
      Previous value: -"Folder to save into, absolute or relative to /app. Default: launch-film-{host}. 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."New value: +"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."
    • changedInput schema / properties / seconds / description
      Previous value: -"Aim for this length (default 30)."New value: +"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."
    • changedInput schema / properties / url / description
      Previous value: -"The product's website, like https://linear.app"New value: +"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."
    • 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 / words / description
      Previous value: -"A words.json you already have, instead of reading the page again."New value: +"A words.json from an earlier plan or film, used instead of reading the page again, so a second aspect keeps the same words."
    • 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. Changed3 schema fields changed
    • changedInput schema / properties / out_dir / description
      Previous value: -"Folder to save into, absolute or relative to /app. Default: launch-film-{host}."New value: +"Folder to save into, absolute or relative to /app. Default: launch-film-{host}. 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."
    • addedOutput schema / properties / expires_at
      Added value: +{
      +  "description": "When the download links stop working.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / files / items / properties / url
      Added value: +{
      +  "description": "Where to download the file, when the job ran on a server.",
      +  "type": "string"
      +}
  3. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations mark this destructive and non-idempotent, and the description backs that up with specifics: a run replaces files an earlier run left in out_dir, deletes and remakes brand/, and refuses to start when brand/ holds an unlisted file in any letter case. It also discloses that nothing is rendered and that the result surfaces film.json, words.json and brand/BRAND.md for checking against the page — real behavioral context beyond the hints.

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 when-to-use clause, then purpose, then artifact/verification, then alternatives. Dense but each sentence carries routing or workflow information; the trailing version/chassis parenthetical and the slight overlap between the render guidance and the make_launch_film exclusion are the only filler.

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 10-parameter, destructive, open-world tool with an output schema already present, the description covers purpose, trigger, artifact outputs, failure/refusal conditions, correction workflow, aspect planning, and sibling routing. Return values are correctly left to the output schema.

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 baseline is 3, but the description adds cross-parameter workflow meaning the schema only states piecemeal: a second aspect is a separate plan reusing words from the first, and film.json should be hand-corrected (via launch_film_guide topic types) before rendering. That sequencing is not obvious from the per-field descriptions alone.

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?

"Reads a product's brand and page and writes film.json, the plan of a launch film, without rendering it" names a concrete verb (plan/write) and a concrete artifact (film.json), and explicitly contrasts with rendering. It is immediately distinguishable from siblings make_launch_film (one job) and render_launch_film (renders).

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?

States the trigger condition ("when the user wants to choose a launch film's look, length or words, or to read its plan before it renders") and names the alternatives with selection rules: make_launch_film for a one-job film, render_launch_film to render, launch_film_guide for scene/look types, makersmcp_playbook for the whole job. No inference needed.

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