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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

app_event_screenshots_get_instance

Retrieve a specific App Store app event screenshot by ID, including file, asset, delivery, and localization details with optional related fields.

Instructions

GET /v1/appEventScreenshots/{id} (GET /v1/appEventScreenshots/{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_event_screenshots_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_appEventScreenshotsNothe fields to include for returned resources of type appEventScreenshots
fields_appEventLocalizationsNothe fields to include for returned resources of type appEventLocalizations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.7/5.0
Behavior1/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, and it discloses nothing: not the read-only nature, not whether the ID is a resource ID versus an App Store ID, not auth requirements, not error behavior for missing IDs. Repeating the URL template adds no behavioral context.

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 the parenthetical simply repeats the identical path string, so half the content is pure redundancy with zero informational value. Brevity here stems from under-specification rather than disciplined conciseness.

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

Completeness1/5

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

With no annotations, no output schema, and a sparse description, an agent gets nothing about what a successful response contains, what include/fields affect, or how the returned app event screenshot relates to localizations. Completely inadequate for a 4-parameter retrieval tool.

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 id, include, fields_appEventScreenshots, and fields_appEventLocalizations in reasonable detail. The description adds nothing beyond the schema, but the high coverage establishes the baseline of 3.

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 just the HTTP method and path duplicated verbatim: 'GET /v1/appEventScreenshots/{id} (GET /v1/appEventScreenshots/{id})'. It restates the tool name (get_instance on app_event_screenshots) without explaining what an app event screenshot resource is or what retrieving one yields. This is tautology rather than an explanation of purpose.

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

Usage Guidelines1/5

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

No guidance whatsoever on when to use this tool versus the many siblings, such as app_event_localizations_app_event_screenshots_get_to_many_related or app_event_screenshots_update_instance. There is no mention of prerequisites, ID sourcing, or when a related/collection call is preferable.

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