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. |
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 5 tools
Each tool has a clearly distinct role: listing presets, composing a single screenshot, generating a batch, creating a showcase strip, and validating an image. There is no overlap in purpose, and the descriptions reinforce these boundaries.
All tool names follow a snake_case verb_noun pattern, but the verbs are mixed in style (list, compose, generate, create, validate). While 'compose' and 'generate' are near-synonyms, the noun targets differ enough to avoid confusion. Minor inconsistency but overall predictable.
Five tools is well-scoped for a specialized domain. Each tool addresses a distinct step in the screenshot generation workflow, and none feel redundant or missing. This is an ideal size for a focused MCP server.
The tool surface covers the full lifecycle: discovery (list_presets), creation (compose_screenshot, generate_set), presentation (create_showcase), and verification (validate_screenshot). There are no obvious gaps for the stated purpose of generating store-ready marketing screenshots.