Skip to main content
Glama

Launch pictures

make_launch_stills
Destructive

Generates launch images at the exact sizes Product Hunt, link previews, X, Google Play and the Chrome Web Store require, saved as opaque PNGs with a STILLS.md index.

Instructions

Use it when the user wants Product Hunt gallery images and thumbnail, an og:image, an X post image, a Google Play feature graphic or Chrome Web Store tiles. Makes the pictures a launch needs at the exact size each place asks for, as opaque PNGs in stills/, listed in STILLS.md, which the result shows. ph makes ph-1.png (the logo, the promise and the screen) and up to 5 of the film's scenes from ph-2.png on, all 1270x760, and ph-thumbnail.png at 240x240; og makes og.png at 1200x630; x makes x.png at 1600x900; play makes play-feature.png at 1024x500, Google Play's feature graphic only; chrome makes chrome-small.png at 440x280 and chrome-marquee.png at 1400x560. The words and the look come from a film.json, the logo from the brand and the screen from the site; no picture is 9:16. Given a site instead of a film.json, it plans a film first with the default look, length and aspect. For App Store or Google Play screenshots, use take_screenshots 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": {
      "source": "<source>"
    },
    "name": "make_launch_stills"
  }
}

Input Schema

NameRequiredDescriptionDefault
forNoWhich places to make pictures for (default all of them): ph, the Product Hunt gallery and thumbnail; og, a link preview; x, a post on X; play, the Google Play feature graphic; chrome, the Chrome Web Store tiles.
sourceYesThe product's website, like https://linear.app, or a film.json you already have, so the pictures match that film. Given the website, it plans a film first with the default look, length and aspect; stills/ goes next to the film.json. The address needs a dot in its host name, so localhost on its own is refused.
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. Given a file instead of an address, the kit saves in the folder of source and takes no out_dir. The kit deletes the brand/ folder in it and makes it again 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.
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. Changed8 schema fields changedv0.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / for / description
      Previous value: -"Which places to make pictures for (default all of them)."New value: +"Which places to make pictures for (default all of them): ph, the Product Hunt gallery and thumbnail; og, a link preview; x, a post on X; play, the Google Play feature graphic; chrome, the Chrome Web Store tiles."
    • changedInput schema / properties / out_dir / description
      Previous value: -"Folder to save into, absolute or relative to /app. Default: launch-film-{host}. Given a file instead of an address, the kit saves in the folder of source and takes no out_dir. The kit deletes the brand/ folder in it and makes it again 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."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. Given a file instead of an address, the kit saves in the folder of source and takes no out_dir. The kit deletes the brand/ folder in it and makes it again 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."
    • changedInput schema / properties / source / description
      Previous value: -"The product's website, like https://linear.app, or a film.json you already have, whose stills/ go next to it."New value: +"The product's website, like https://linear.app, or a film.json you already have, so the pictures match that film. Given the website, it plans a film first with the default look, length and aspect; stills/ goes next to the film.json. The address needs a dot in its host name, so localhost on its own is refused."
    • 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."
    • 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. Changed4 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}. Given a file instead of an address, the kit saves in the folder of source and takes no out_dir. The kit deletes the brand/ folder in it and makes it again 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."
    • changedInput schema / properties / source / description
      Previous value: -"The product's website, or a film.json you already have."New value: +"The product's website, like https://linear.app, or a film.json you already have, whose stills/ go next to it."
    • 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?

Beyond the annotations, it discloses concrete side effects: opaque PNGs written to stills/, an STILLS.md listing, that a run replaces files an earlier run left in out_dir, and that brand/ is deleted and rebuilt for App Store pages. These details align with and enrich the destructiveHint/openWorld signals rather than contradicting them.

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?

Usage and trigger list are front-loaded, then outputs are enumerated compactly. The out_dir sentence is dense and slightly rambling about kit-owned files and case-insensitive collisions, which costs some readability, but nearly every clause carries useful information.

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 complex multi-output generation tool with an output schema, the description covers inputs (site vs film.json), outputs and their sizes, side effects, the alternative tool, and where to find the full playbook. Nothing an agent needs to invoke 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 baseline is 3, but the description adds real meaning: it explains source accepts either a site or film.json and how stills/ is placed, and it flags the out_dir collision/replacement semantics. It does not fully restate the enum meaning of 'for', but the schema already covers that.

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 ('Makes the pictures a launch needs') and enumerates concrete outputs with exact dimensions for each platform variant (ph, og, x, play, chrome). An agent can tell exactly what it produces and at what sizes, and it is clearly differentiated from take_screenshots.

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?

Opens with an explicit when-to-use trigger list (Product Hunt gallery, og:image, X post, Play feature graphic, Chrome tiles) and names the alternative 'take_screenshots' with the condition that selects it. It also points to the playbook and notes that a site input triggers film planning first.

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