Claude can already write your screenshot headlines. With the Shotlingo connector it can also do the work around them: read your live listing, translate the set, check that every language still fits, render it, size an A/B test and upload the result. This page lists 11 of those jobs. Each one names the tool Claude calls and gives you a prompt you can paste as is.
Everything below is what the connector does today. The full tool reference lives on the Shotlingo MCP page.
Before you start: connect Shotlingo to Claude
- In Claude (web, desktop or Code), open Settings, then Connectors, then Add custom connector.
- Paste
https://mcp.shotlingo.com/mcpand sign in with your Shotlingo account. - Start a new chat. Connectors attach when a session starts, so a chat that was already open will not see the tools.
The connector needs a Pro, Plus or Studio plan. Renders come out of the same daily counter as the web editor: 30 a day on Pro, 150 on Plus, no cap on Studio. Store uploads, live screenshot import and Product Page Optimization tests need Plus or Studio. Any other MCP client works too. Point it at the same URL over Streamable HTTP and it handles the sign-in itself.
A good first prompt, so you know your budget for the day (tool: get_usage):
Use Shotlingo. How many renders and store uploads do I have left today?1. Pull your live screenshots into an editable project
Claude reads the screenshots that are live on your App Store page for one locale and brings them in as pages. It uses your own App Store Connect key and only reads. These are the finished marketing images, the same ones a shopper sees. Tool: import_store_screenshots.
Use Shotlingo. Create a project called "[app name] rework". Import the live App Store screenshots of [app name] for en-US into it as pages. Then tell me how many pages came in and what each headline says.2. Start from a community template
Claude lists the approved templates, opens the one you pick and clones it into a new project with its pages. Tools: list_templates, get_template, adapt_template.
Use Shotlingo. Show me community screenshot templates that would suit a [kind of app] app. When I pick one, clone it into a new project for [app name] and list its text slots.3. Build a page from one raw app screen
Give Claude a public link to a screenshot of your app. It downloads the image and builds a whole page around it: headline, device and caption, placed the way a store screenshot is. The layouts are headline-device-caption, headline-device and headline-only. Images can be PNG, JPEG, WebP or GIF up to 8 MB. Tools: create_project, import_image, generate_page, apply_device_frame.
Use Shotlingo. Create a 1290x2796 project called "[app name] v2". Import this screen: [https link]. Build page 1 with the headline-device-caption layout. Headline: "[headline]". Caption: "[caption]". Render it and show me the preview.4. Make a copy before you touch a live design
Every edit tool writes straight to the project, and there is no undo. A copy keeps the original as your way back. Tool: duplicate_project.
Use Shotlingo. Duplicate my project "[project name]" and make every edit in this chat on the copy only.5. Rewrite every headline in one pass
Claude reads each page's text slots, with their ids and current text, then saves your new copy. The fit check below doubles as the way to read a project's structure. Tools: fit_text_into_design, update_element, set_translations.
Use Shotlingo. Read every text slot in "[project name]". Rewrite each headline in 5 words or fewer, each one naming a single thing the user gets. Show me the old and new lines side by side and wait for my yes before you save.6. Translate the set and check that every language still fits
For many languages at once, Claude gets the largest font size each translated line still fits at, and the slots that cannot fit at all. This check renders nothing and uses no quota. It is an estimate: the renderer refits with the real fonts at render time, and that result wins. The connector covers 41 languages. Tools: fit_text_into_design, set_translations.
Use Shotlingo. Translate the headlines and captions in "[project name]" into German, French, Japanese, Korean and Brazilian Portuguese. Keep each line about as short as the English. Check the fit in every language, shorten any line that does not fit, then save the translations.7. Render one page and look at it in the chat
A render returns a PNG link. Ask for an inline preview and Claude also shows you the picture in the conversation, shrunk to 480 px wide. Tool: render_screenshot.
Use Shotlingo. Render page 1 of "[project name]" in Japanese at 1290x2796 with an inline preview. Tell me if any line is cut off or wraps badly.8. Render a page into every language at once
A batch renders the same page in many languages as background steps that retry on their own. Claude checks the batch and collects the image link for each language. Tools: start_batch, get_batch_status.
Use Shotlingo. Render page 1 of "[project name]" in every language it has, as one batch. Check the batch until it is done and give me a table of language and image link.9. Find out if an A/B test can finish before you start one
On a small app, a screenshot test can run its whole length and still show no result. Ask first. Claude works out the smallest effect your traffic could detect at 7, 14, 28, 56 and 90 days, and how long a target lift would need. It is pure math, with no render and no quota. Your daily impressions and conversion rate are in App Store Connect under Analytics. Tool: estimate_ab_test. If you would rather do it by hand, use our A/B test sample size calculator.
Use Shotlingo. My product page gets about [impressions] impressions a day and [conversion rate]% of viewers download. What is the smallest lift a screenshot test could detect at 14, 28 and 56 days? Is a test worth running?10. Put a new design into a Product Page Optimization test
Claude uploads your design as a treatment in Apple's Product Page Optimization, so the live page stays as it is while the test runs. The first call is a preview, and it names any running test it would stop. Nothing changes until you confirm. Needs Plus or Studio. Tools: list_ab_tests, create_ab_test.
Use Shotlingo. List the Product Page Optimization tests on [app name]. Then preview a new test called "[test name]" with the renders from "[project name]" as the treatment. Show me the preview and wait for my yes before you create it.11. Upload the finished set to App Store Connect or Google Play
Claude uploads the rendered screenshots to your listing for the locales you name. This replaces the screenshots of that device size on the live store, and neither store has an undo. So both tools work in two steps: the first call shows what would be replaced, and only a second call with your confirmation writes. Needs Plus or Studio. Tools: list_app_store_apps, export_to_app_store, list_google_play_apps, export_to_google_play.
Use Shotlingo. Find [app name] in my App Store Connect apps. Preview an upload of the renders from "[project name]" for en-US, de-DE and ja. Show me exactly what will be replaced and wait for my yes.One prompt for the whole run
Use Shotlingo. Check my render budget for today. Duplicate "[project name]" and work only on the copy. Read every text slot, translate the headlines and captions into [languages], fix any line that does not fit, and save. Render page 1 in every language as a batch and show me one preview per language. Do not upload anything or start a test until I say so.What Claude still needs from you
- The words that matter. Claude drafts fast. You know which feature your users came for, so read every headline before it ships.
- The final yes on anything live. Store uploads and PPO tests always stop at a preview first.
- A look at the renders. The fit check is an estimate. The preview is the real picture.
The full tool list, plan limits and a worked run are on the Shotlingo MCP page.