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_relationship

Fetch the image relationship for a subscription version using its ID to identify the linked image resource in App Store Connect.

Instructions

GET /v1/subscriptionVersions/{id}/relationships/image (GET /v1/subscriptionVersions/{id}/relationships/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_relationship"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. "GET" implies a non-destructive read, but the description says nothing about return shape, pagination, permissions, or that relationship endpoints return linkage objects rather than the image itself. The route echo conveys essentially nothing behavioral.

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 content is duplicated verbatim inside parentheses, which is pure waste. There is no front-loaded explanatory sentence, only a raw route.

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?

With no annotations, no output schema, and dozens of near-identical relationship/related siblings, the description leaves an agent unable to choose correctly or predict the response. It should clarify that this returns the to-one image linkage for a subscription version.

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?

There is a single parameter (id) whose schema description coverage is 100%, so the schema already explains it. Per the baseline rule, a 3 is appropriate since the description adds no parameter meaning but nothing is missing either.

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 only the HTTP route repeated twice: "GET /v1/subscriptionVersions/{id}/relationships/image". It names the resource (subscription version image relationship) but never states in prose what the call does or returns, so the agent must reverse-engineer intent from a path string.

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 on when to use this vs the close sibling subscription_versions_image_get_to_one_related, whose distinction (linkage IDs vs full resource) is exactly what an agent needs. Nothing about prerequisites or alternatives is provided.

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