StoreShots
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_stylesA | List the curated screenshot styles (ids for generate_screenshots.style) with colours and layouts. |
| list_devicesA | List device frames (iphone, iphone-duo, android, ipad) and store output targets (ios-6.9 1320x2868, ios-6.5 1242x2688, android-phone, ipad-13). |
| generate_screenshotsA | Turn 1–5 raw app screenshots (local file paths or http(s) URLs) into framed App Store / Google Play marketing screenshots with headlines. One call = one set (all requested sizes) = 1 credit; free keys get 3 watermarked sets per month. Returns a jobId; set download_to (or call get_output) to save the PNGs/ZIP locally. |
| get_outputA | Download a job's ZIP and/or individual PNGs to a local directory (default ~/StoreShots/). Jobs expire after 24h. |
| get_balanceA | Show remaining paid credits, free generations left this month, and available credit packs. |
| buy_creditsA | Return the Stripe Payment Link for a credit pack, personalised for this API key (client_reference_id + prefilled email). Nothing is charged by this tool — give the link to the user to pay in their browser; credits are added automatically after payment. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: two reference listers (styles vs devices), one generation action, one output retrieval, and two billing operations. No overlapping functionality; an agent can easily select the right tool.
All tool names follow a consistent snake_case verb_noun pattern (list_*, generate_*, get_*, buy_*). No deviations or mixed conventions.
Six tools cover the full workflow without redundancy: two lookups, one core action, one retrieval, and two billing helpers. Well-scoped for the service.
The surface covers style/device discovery, generation, output download, and credit management. Minor gap: no explicit job status or history tool, though get_output implies retrieval; agents can work around this.