Skip to main content
Glama
kapillamba4

app-store-screenshots-mcp

generate_screenshot

Compose store-ready screenshots by overlaying user app UI with AI-generated backgrounds, clipart, and captions. Writes platform-specific PNGs.

Instructions

Compose one store screenshot from user app UI + YOUR in-session AI assets (background, clipart, titles, alignment). Writes opaque PNGs at store sizes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandNo
labelNoAI-written small category label above the headline
sizesNoSize ids from list_export_sizes, e.g. ["ios-6.9"]. Defaults to platform primary.
layoutNoLayout template. Use custom + devicePlacement/captionStyle for fully AI-directed alignment. Vary across slides.
clipartNoAI-generated decorative images (clipart, icons, stickers, blobs) with positions. Generate in the same session.
gradientNoOptional CSS gradient under/over AI background; also used when backgroundImage omitted
headlineYesAI-written headline. Use \n for line breaks. 3–5 words per line, one idea.
platformYesTarget store platform
vignetteNoSoft dark vignette for text contrast (default true when backgroundImage set)
outputDirYesAbsolute directory path to write PNG files
deviceFrameNoDevice frame style. Defaults: iphone for ios, android for android.
subheadlineNoAI-written subtitle under the headline
captionStyleNoAI-chosen title/subtitle alignment and placement
appScreenshotYesAbsolute path to the in-app screenshot PNG/JPG (user-provided)
filenamePrefixNoFilename prefix, e.g. "01-hero" (default: "screenshot")
backgroundColorNoSolid fallback only if no AI background/gradient
backgroundImageNoREQUIRED for best quality: absolute path to AI-generated background for this slide (same session). Portrait ~master size.
devicePlacementNoAI-chosen phone position overrides (use with any layout; required for layout=custom)
appScreenshotSecondaryNoOptional second screenshot for two-phone layout
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, leaving the description to carry the full burden. It mentions writing PNG files and using 'in-session AI assets', but does not disclose side effects (e.g., overwriting behavior), required permissions, or behavior on failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that front-loads the main action and lists key inputs. It is relatively concise with no wasted words, though it could be slightly more streamlined.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (19 parameters, nested objects) and lack of output schema, the description covers the essential inputs and output but does not detail behavioral aspects like layout options or the need for in-session asset generation. Schema descriptions fill some gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 95%, so baseline is 3. The description adds high-level context (combining user screenshot with AI assets) but does not provide parameter-specific meaning beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Compose', the resource 'one store screenshot', and specifies inputs (user app UI, AI assets) and output (opaque PNGs at store sizes). It distinguishes from sibling 'generate_screenshot_set' by implying single screenshot vs. multiple.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for composing a single screenshot with AI assets but does not explicitly state when to use this tool versus alternatives like generate_screenshot_set. No when-not guidance or mention of prerequisites is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kapillamba4/app-store-screenshots-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server