storeshots-mcp
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_presetsA | Returns all supported platform presets with their store, exact output dimensions, and layout metrics. Call this first to decide which presets to generate. |
| compose_screenshotA | Renders one store-ready marketing screenshot: brand background, headline (verb + descriptor, auto-uppercased for the given language), and the app screenshot inside a device frame. Output has exact store dimensions for the chosen preset. |
| generate_setA | Batch-renders an ordered screenshot set for one preset and language. Item N becomes {lang}_{NN}.png. Returns per-item results plus any warnings. |
| create_showcaseA | Composes a horizontal preview strip from generated screenshots, for READMEs, decks, and social posts. The result includes a |
| validate_screenshotA | Checks an image against store requirements: exact preset dimensions, PNG/JPEG format, no alpha channel. Without a preset id, reports which preset the dimensions match. |
| build_projectA | Renders a whole store listing from a storeshots.json config: every screen x preset x language, plus an optional feature graphic and showcase strips. Re-renders only outputs whose inputs changed and removes outputs of deleted screens. Config shape: {"background":"#hex","presets":["ios-phone","android-phone"],"languages":["en","tr"],"outputDir":"output","screens":[{"screenshot":"shots/home.png","copy":{"en":["Track","your daily mood"],"tr":["Takip et","ruh halini"]},"variant":"tilted"}],"panorama":{"to":"#hex"},"featureGraphic":{"screen":1},"showcase":true}. Screenshot paths are relative to the config and may use {lang}, {preset}, {platform} (ios|android). Prefer this over generate_set when the user will iterate on a set. If the result includes a |
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 distinct scope: discovery (list_presets), single render (compose_screenshot), batch (generate_set), strip (create_showcase), validation (validate_screenshot), full project (build_project). The three rendering tools differ by granularity, and build_project explicitly tells the agent to prefer it over generate_set, which resolves most overlap. Only mild potential confusion remains between generate_set and compose_screenshot.
All six tools follow a consistent snake_case verb_noun pattern: list_presets, generate_set, compose_screenshot, create_showcase, validate_screenshot, build_project. The verbs vary appropriately by action while the structural convention is uniform throughout.
Six tools is well-scoped for a screenshot-generation server, covering discovery, single/batch/project rendering, showcase composition, and validation. Each tool earns its place with no redundant entries.
The surface covers a full lifecycle: preset discovery, single and batch rendering, whole-project builds with incremental re-render and cleanup of deleted outputs, showcase composition, and store-requirement validation. No obvious gaps in the screenshot-generation domain.