Make a promo
make_promoMakes a 15 to 30 s studio-style promo of a web app, a phone app, a new feature or a shop's product from its site or brand kit, in 9:16 first: brand kit (imported from the site if there is none, 2 credits), the app's screens, a recipe, the lines and the checks, then a draft. It needs real screens of the product: public pages of the app itself (app_pages, captured at 2 credits a page) or screenshots and recordings from the person. When it has too few, it renders nothing and says what it needs, with an upload link and a recording link; call it again with promo_id when they're in. The draft is priced per scene (3 credits per started 2 s, nothing for a scene already rendered) plus 10 to put it together: about 43 to 49 credits for a web app, 43 to 49 for a phone app, 46 for a feature launch and 49 for a shop's product for a first 9:16. A phone app takes phone screenshots, taps made from two screenshots (pairs) and store links; a feature launch takes the feature's name and a real screenshot from before it (old_screens); a shop's product takes its product page (product_page), or the person's photos, name and price (product). estimate_only gives the range first and spends nothing. Screenshots the person attached: in Claude, send them from your code sandbox to upload_post_url first (get_promo's next says how), without asking for them again; in ChatGPT pass them in files. For screens not attached yet, add_screens shows an upload box in the chat. Returns the promo as get_promo does.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "make_promo"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | The product's public site, e.g. https://dividendmapper.com | |
| files | No | ChatGPT only: images the person attached to the chat. Leave out in other apps | |
| lines | No | Your own lines, checked like the writer's: one outcome per feature | |
| model | No | The line writer's model (owner only) | |
| notes | No | What to say: the line writer's brief | |
| pairs | No | Up to 3 taps or clicks, each from two of the person's screenshots of the same screen (a phone app's tap scene, or a click on a web app): 2 credits each when made, nothing if the control isn't found | |
| sizes | No | The sizes the person wants, for the prices (all four by default) | |
| sound | No | Music, sound effects and voice | |
| lineup | No | One of the recipe's line-ups (list_recipes lists each with what it requires). Left out, the first the material meets; when none is met, the promo says what to send. A Quick line-up (list_recipes marks it) is used only when named, and sets its recipe; the promo stays Quick until a full line-up is named or null is passed, which goes back to the first full line-up the material meets | |
| recipe | No | The recipe: saas (a web app), mobile (a phone app), feature-launch (a new feature of a product) or ecom (a product in an online shop). Left out, the tool picks from what it is given and says which | |
| stores | No | A phone app's store pages: the end card shows each store's badge | |
| feature | No | The new feature's name, as the product calls it (feature launch) | |
| product | No | The product as the person gives it: for marketplaces, or a shop capture can't read. Shown as given, marked as theirs. On a promo that has one, the fields left out are kept, even when the name changes: for another product, give each field (null for none) | |
| screens | No | Up to 8 screenshots of the app, added to the brand kit | |
| brand_id | No | Or a brand kit, by id or name | |
| promo_id | No | Carry on with this promo: new screens, or after a needs reply | |
| app_pages | No | Up to 4 public pages that show the product itself working (a public demo, tool or dashboard page), never the home page, product marketing or pricing (those go in site_pages, for a Quick promo), and never a login page; captured at 2 credits a page. For an app behind a login, leave this out and ask the person for screenshots or the recording link | |
| site_pages | No | Quick promos only: up to 3 public pages of the person's own site to make it from, 2 credits a page. Left out, the address itself. Home, product and pricing pages belong here, never in app_pages | |
| old_screens | No | Screenshots of the product from before the feature, the same kind of screen as the new ones (feature launch); they are only ever shown as the before | |
| product_page | No | The product's own page in the shop (ecom), e.g. https://shop.example/products/tote; captured with its photos, price and rating at 2 credits. null takes it off the promo | |
| wait_seconds | No | How long to wait for the promo to settle (default 45) | |
| estimate_only | No | Give the price range and the screens check (which screens can't be used, by their size), and spend nothing | |
| other_products | No | Up to 3 other product pages from the same shop, for the grid (ecom); 2 credits each |