Skip to main content
Glama
Sign In
app-store-screenshots-mcp

app-store-screenshots-mcp

by kapillamba4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_session_design_guide

Plan app store screenshots: get per-slide layout suggestions, AI background prompts, clipart prompts, copy rules, and alignment guidance. Call this before generating images.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "appName": "<appName>",
      "features": "<features>",
      "styleDirection": "<styleDirection>"
    },
    "name": "get_session_design_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNameYesApp name
hasIpadNo
featuresYesFeatures in priority order (one idea per slide)
platformNoios
slideCountNoHow many screenshots (default: min(features, 6))
brandColorsNoBrand hex colors if known
styleDirectionYesStyle: e.g. warm/organic, dark/moody, clean/minimal, bold/colorful, gradient-heavy

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations exist, so the description must carry the transparency burden. It describes the tool as returning a plan, implying it is non-destructive and safe, but does not explicitly state idempotency, side effects, or auth requirements—adequate but not thorough.

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

Conciseness5/5

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

Two sentences with critical information front-loaded ('START HERE'), no filler—every word serves a purpose.

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

Completeness5/5

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

No output schema exists, but the description enumerates what the tool returns (layout suggestions, prompts, rules, guidance) and places it in a workflow context, making it sufficiently complete for safe invocation.

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?

With 71% schema description coverage, baseline is 3. The description adds no parameter-specific details beyond what the schema already provides, thus not improving parameter understanding.

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 it returns a 'same-session plan' with specific content (layout suggestions, prompts, rules, guidance) and positions itself as the starting point ('START HERE'), distinguishing it from sibling tools that generate screenshots.

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

Usage Guidelines5/5

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

Explicitly instructs the agent to 'Call this before generating any images or composing screenshots', providing direct guidance on when to use this tool relative to others.

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

Deploy Server

Other Tools