app-store-screenshots-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 |
|---|---|
| get_session_design_guideA | START HERE. Returns a same-session plan: per-slide layout suggestions, AI background prompts, clipart prompts, copy rules, and alignment guidance. Call this before generating any images or composing screenshots. |
| list_export_sizesA | List supported App Store and Play Store screenshot export sizes (ids, labels, dimensions). |
| list_layoutsA | List layout templates including custom (AI-directed). Prefer get_session_design_guide for a full creative plan. |
| generate_screenshotA | Compose one store screenshot from user app UI + YOUR in-session AI assets (background, clipart, titles, alignment). Writes opaque PNGs at store sizes. |
| generate_screenshot_setB | Compose a full ordered set (1–10). Each slide should include AI-written copy, AI background path, optional AI clipart, and AI-chosen layout/alignment. Writes numbered PNGs + manifest.json. |
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 distinct purpose: generating single or multiple screenshots, retrieving a design guide, listing export sizes, and listing layout templates. No overlapping functionality, making selection unambiguous.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., generate_screenshot, get_session_design_guide). The naming is predictable and uniform across the set.
With 5 tools, the set is appropriately scoped for the domain of generating app store screenshots. Each tool fills a necessary role without redundancy or deficiency.
The tool set covers the full workflow: planning via design guide, configuration via export sizes and layouts, and execution via single or batch screenshot generation. No obvious gaps for the intended purpose.