Generate screenshot set
generate_screenshot_setDesign a finished App Store / Google Play screenshot set from uploaded screenshots. Step 2 of 3.
Returns immediately with a review link while the set is designed in the background (about 1–2 minutes) — then call get_screenshot_set to wait for it. The result is three art directions sharing one set of headlines, each fully editable in the LaunchShots editor.
Write app_description from the real source: the README, store listing, or the app's own copy — what it does, who it's for, and what makes it different. Specific beats generic; the headlines are only as sharp as this.
Either pass set_id from prepare_screenshot_upload (preferred), or pass the screenshots inline as base64 if you cannot run shell commands (keep each under ~1 MB). Calling again with the same set_id after a failure retries it; nothing is charged for a failed run.
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": {
"app_name": "<app_name>",
"app_description": "<app_description>",
"platform": "<platform>"
},
"name": "generate_screenshot_set"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| set_id | No | The set_id from prepare_screenshot_upload, once its screenshots are uploaded. | |
| app_name | Yes | The app’s name as it appears in the store. | |
| language | No | Store language to write the headlines in, e.g. en-US, de-DE, ja, pt-BR. Defaults to en-US. | |
| platform | Yes | ios for the App Store, android for Google Play. | |
| style_note | No | Optional art direction, e.g. "dark and premium", "playful, uses our brand orange #FF6B00". | |
| screenshots | No | Only if you cannot upload with prepare_screenshot_upload: the screenshots inline, each under ~1 MB. | |
| include_tablet | No | Also produce the matching iPad / Android tablet set. Counts as a second generation; needs an API key. | |
| app_description | Yes | What the app does, who it is for and what sets it apart — 2–6 specific sentences drawn from the README, store listing or product copy. |