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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subscription_versions_image_get_to_one_related

Retrieve the image for a specific subscription version using its ID to support App Store Connect asset management.

Instructions

GET /v1/subscriptionVersions/{id}/image (GET /v1/subscriptionVersions/{id}/image)

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": "subscription_versions_image_get_to_one_related"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
fields_subscriptionImagesNothe fields to include for returned resources of type subscriptionImages

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.8/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 burden of behavioral disclosure, and it discloses nothing: no read-only confirmation, no auth requirements, no note about what resource is returned or what the fields_subscriptionImages parameter does. A bare endpoint path is not 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 structure is wasteful: the identical path string appears twice, once bare and once in parentheses, adding zero information. Brevity here reflects under-specification rather than effective conciseness.

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 relationship-fetch tool with no output schema and no annotations, the description should at minimum state what is returned (the subscription image resource for a subscription version). It provides neither the resource semantics nor the relationship direction, leaving the agent to infer everything from the name.

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 both parameters (id and fields_subscriptionImages) are documented in the schema itself, so the baseline of 3 applies. The description adds nothing beyond the {id} path token, but it does not need to compensate for a schema gap.

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 raw HTTP route 'GET /v1/subscriptionVersions/{id}/image' repeated verbatim in parentheses. It restates the tool name rather than stating in plain language what the tool retrieves, and it gives no basis for distinguishing this from sibling subscription_versions_image_get_to_one_relationship or subscription_versions_images_get_to_many_related.

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?

There is no when-to-use guidance, no prerequisites, and no mention of any alternative tool. An agent must guess from the name alone whether this returns the single related image or something else.

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