Skip to main content
Glama
Sign In
App Store Connect MCP Server

App Store Connect MCP Server

by yunyang088
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_app_screenshots

Retrieve all screenshots in a specified App Store Connect screenshot set by ID, with an optional limit. Use it to inspect or manage app listing visuals.

Instructions

List all screenshots in a screenshot set

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": {
      "appScreenshotSetId": "<appScreenshotSetId>"
    },
    "name": "list_app_screenshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of screenshots to return (default: 100)
appScreenshotSetIdYesThe ID of the screenshot set

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.3

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'List all screenshots' implies a read-only operation, but it omits pagination behavior, auth requirements, default limit effects, and any return shape—leaving most behavioral traits unstated.

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?

A single, front-loaded sentence with no filler. For a simple list tool, this is appropriately sized and every word 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?

The tool is low-complexity with 100% schema coverage and no output schema, so the core call is clear. But with no annotations and no output schema, the description should provide more behavioral context (e.g., pagination or read-only guarantee) to be fully complete.

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%, so both the limit and appScreenshotSetId parameters are already documented. The phrase 'in a screenshot set' loosely maps to appScreenshotSetId but adds no syntax or constraints beyond the schema, making the baseline 3 appropriate.

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

Purpose4/5

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

States a specific verb ('List') and resource ('screenshots in a screenshot set'), which distinguishes it from list_app_screenshot_sets. However, it does not explicitly name or contrast with any sibling, so it stops short of a 5.

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

Usage Guidelines2/5

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

Provides no when-to-use guidance, no alternatives, and no prerequisites. The only implied context is that an existing screenshot set ID is needed, but the agent is not routed between this and related tools like list_app_screenshot_sets.

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