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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

app_screenshot_sets_get_instance

Retrieve a specific App Store screenshot set by ID and optionally include related localizations or screenshots to inspect app store media metadata.

Instructions

GET /v1/appScreenshotSets/{id} (GET /v1/appScreenshotSets/{id})

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": {
      "id": "<id>"
    },
    "name": "app_screenshot_sets_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
limit_appScreenshotsNomaximum number of related appScreenshots returned (when they are included)
fields_appScreenshotsNothe fields to include for returned resources of type appScreenshots
fields_appScreenshotSetsNothe fields to include for returned resources of type appScreenshotSets
fields_appStoreVersionLocalizationsNothe fields to include for returned resources of type appStoreVersionLocalizations
fields_appCustomProductPageLocalizationsNothe fields to include for returned resources of type appCustomProductPageLocalizations
fields_appStoreVersionExperimentTreatmentLocalizationsNothe fields to include for returned resources of type appStoreVersionExperimentTreatmentLocalizations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.2/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 behavioral burden, yet it discloses nothing beyond the raw path. The GET prefix implies a read, but there is no mention of authentication requirements, pagination of included relationships, rate limits, or what happens for a missing id.

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

Conciseness2/5

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

It is short, but that brevity reflects under-specification rather than efficiency. The same endpoint string is duplicated parenthetically, which is wasted tokens and not front-loaded with any useful information.

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

Completeness2/5

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

For a GET tool with 8 parameters, relationship includes, and no annotations or output schema, the description is inadequate. It leaves behavioral context such as auth, pagination, and error behavior entirely unspecified.

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 the schema already documents all 8 parameters including the include and fields_* relationship options. The description adds no additional parameter semantics, so the baseline of 3 is appropriate.

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

Purpose2/5

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

The description is essentially the endpoint path repeated twice: 'GET /v1/appScreenshotSets/{id}'. It technically identifies a verb (GET) and a resource (appScreenshotSets), but it restates the tool name and gives no plain-language explanation of what the call returns. It also fails to distinguish this from sibling tools like app_screenshot_sets_app_screenshots_get_to_many_relationship or app_screenshot_sets_create_instance.

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?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites, and no reference to alternative tools. An agent must infer entirely from the name that this fetches a single app screenshot set by id.

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