Skip to main content
Glama
Sign In

appdesigns App Store screenshots

by click.appdesigns
OverviewDiscussionsAdmin

Put new screenshots in a set

replace_screenshots
Destructive

Use this when a set needs new screenshots in its phones: a recapture, a fixed screen, or a phone frame layer to fill (get_asset shows those as "phone frame: ..."), in a set the user saved (asset_id) or a set or design you made in this conversation (handle). Two calls. First with asset_id or handle and screens (each a screen number, the local file and, for a phone frame layer, its id): it returns one upload command (bash and PowerShell) that sends the files straight to storage. Run it, then call again with the same asset_id or handle, replace_handle and the revision get_asset returned: the files are checked (PNG or JPEG, the shape of the phone's screen) and swapped in, and the reply has the new revision and previews. With asset_id (something the user saved) it needs the user signed in to appdesigns (in Claude Code type /mcp, pick appdesigns and choose Authenticate (or run claude mcp login appdesigns in a separate terminal), in Codex run codex mcp login appdesigns; other agents open the sign-in page themselves); with handle (a set or design you made in this conversation, not saved yet) it needs no sign-in.

Input Schema

NameRequiredDescriptionDefault
handleNoInstead of asset_id: the project_handle create_project returned or the design_handle create_design returned, for something you made in this conversation that the user has not saved yet. Needs no sign-in.
screensNoFirst call: what goes where, at most 6 files a call.
asset_idNoThe asset_id list_projects returned.
revisionNoSecond call: the revision get_asset (or the last edit) returned.
replace_handleNoSecond call: the replace_handle the first call returned, once the upload command has run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses a two-call workflow: the first call returns an upload command, the user runs it, then the second call validates PNG/JPEG files and swaps them in. It explains authentication requirements for asset_id versus handle and notes the reply contains a new revision and previews. This is rich operational detail consistent with destructiveHint=true and idempotentHint=false.

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 front-loaded with the usage condition and all details are relevant to a complex two-step, auth-dependent operation. It is dense and delivered as a single long paragraph, but it avoids repetition and earns most of its length.

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?

For a non-readOnly, destructive, multi-call tool with no output schema, the description covers the complete workflow, validation rules, authentication differences, and return values. It gives an agent everything needed to invoke the tool correctly and interpret the two responses.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful beyond-schema semantics by assigning parameters to specific calls: asset_id/handle and screens in the first call, then asset_id/handle, replace_handle, and revision in the second. It also clarifies that layer is optional and only for phone frame layers.

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 states a specific verb and resource: replacing screenshots in a set's phone screens, including recaptures, fixed screens, and phone frame layers. It distinguishes saved sets (asset_id) from in-conversation sets/designs (handle) and references get_asset for layer IDs, so an agent can identify the tool's scope without opening the schema.

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?

It gives clear when-to-use guidance: when a set needs new screenshots for a recapture, fixed screen, or phone frame layer. It also explains the two-call sequence and auth requirements for each mode. It does not explicitly name a sibling alternative for creating new sets, but the usage context is otherwise well specified.

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