Skip to main content
Glama

appdesigns App Store screenshots

by click.appdesigns
OverviewDiscussionsAdmin

Get the design guide

get_design_guide
Read-onlyIdempotent

Use this when the user wants App Store listing art (an animated product page header, a search result, In-App Event art) or a marketing image (a launch post for X, LinkedIn or Instagram, a link preview, a Play feature graphic) designed for their app and you will draw it yourself. Returns the appdesigns recipe for that asset as markdown: its size and what crops or covers it, the layer format create_design takes (phone frames included), the moves, the quality bar and the hand-off to the user. Read-only; changes nothing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetNoThe asset, as create_design names it: header, search_result, event_card, event_page, x_post, linkedin_post, link_preview, instagram_square, instagram_portrait, instagram_tall, product_hunt, wide_image or play_feature_graphic.header

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / asset / description
      Previous value: -"header (product page header), search_result, event_card or event_page."New value: +"The asset, as create_design names it: header, search_result, event_card, event_page, x_post, linkedin_post, link_preview, instagram_square, instagram_portrait, instagram_tall, product_hunt, wide_image or play_feature_graphic."
    • changedInput schema / properties / asset / enum
      Previous value: -[
-  "header",
-  "search_result",
-  "event_card",
-  "event_page"
-]New value: +[
+  "header",
+  "search_result",
+  "event_card",
+  "event_page",
+  "x_post",
+  "linkedin_post",
+  "link_preview",
+  "instagram_square",
+  "instagram_portrait",
+  "instagram_tall",
+  "product_hunt",
+  "wide_image",
+  "play_feature_graphic"
+]
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so 'Read-only; changes nothing' is largely redundant. However, with no output schema the description usefully discloses what is returned: size, crops/covers, layer format, moves, quality bar, and the hand-off to the user.

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?

Two sentences, front-loaded with the usage condition followed by the return contract. Dense but every clause carries information; the asset enumeration is somewhat long but maps directly to the use cases.

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

Completeness4/5

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

For a simple read-only, single-enum tool with no output schema, the description covers the trigger, the return content, and the safety profile. Minor gaps remain (no mention of error cases or how the recipe relates to subsequent edit/export steps), but nothing essential is missing.

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 100% and the single enum parameter is fully documented in the schema. The description only restates the asset list and the 'as create_design names it' convention already present in the schema, adding no new syntax or format meaning.

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?

States a specific verb+resource: returns the appdesigns recipe (markdown) for a named asset type, and enumerates concrete use cases (listing art, marketing image). It clearly distinguishes itself from create_design by saying the agent 'will draw it yourself' rather than creating the asset.

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

Usage Guidelines4/5

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

Gives explicit trigger conditions ('when the user wants App Store listing art ... or a marketing image') and implies the follow-on flow by referencing the layer format create_design takes. No explicit when-not or named alternative for the actual creation step, so it stops short of a 5.

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

All appdesigns App Store screenshots toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources