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

app-store-screenshots-mcp

by kapillamba4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_layouts

List layout templates for app store screenshots, including AI-directed custom options, to choose a design for your marketing images.

Instructions

List layout templates including custom (AI-directed). Prefer get_session_design_guide for a full creative plan.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_layouts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 provided, so description must carry the burden. 'List' implies read-only, but no explicit statement about safety, auth requirements, or side effects. Minimal behavioral disclosure.

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, no fluff. Key action and sibling alternative front-loaded. Every sentence earns its place.

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?

Simple listing tool with no output schema. Description covers purpose and sibling but omits details about output format, return data, or any caveats. Adequate but could be more complete for an agent.

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

Parameters4/5

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

No parameters in schema (100% coverage), so baseline is 3. Description correctly adds no parameter info, but with zero params, no compensation needed. Score reflects adequate handling.

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?

Verb 'list' clearly indicates retrieval, resource 'layout templates' is specific, and 'including custom (AI-directed)' adds scope. Differentiates from sibling get_session_design_guide via direct mention, making purpose distinct.

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 states when to prefer the alternative tool ('Prefer get_session_design_guide for a full creative plan'), guiding appropriate use. No other exclusions needed.

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