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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

in_app_purchase_images_get_instance

Fetch a specific in-app purchase image by ID from App Store Connect, with optional relationships and field selection for detailed metadata.

Instructions

GET /v1/inAppPurchaseImages/{id} (GET /v1/inAppPurchaseImages/{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": "in_app_purchase_images_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_inAppPurchasesNothe fields to include for returned resources of type inAppPurchases
fields_inAppPurchaseImagesNothe fields to include for returned resources of type inAppPurchaseImages

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.9/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: no authentication requirements, no rate limits, no sparsity/expansion behavior, no note that this is a non-destructive read. Only the HTTP verb is inferable, and that is already in the name.

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 brief but not concise in the useful sense: the single line is a duplicated path expression containing zero informational content, so no sentence earns its place. This is under-specification rather than economical writing.

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?

For a 4-parameter retrieval endpoint with no output schema and no annotations, the description supplies nothing about what the response looks like, how relationships are included, or when it applies. An agent has only the name and schema to work from, leaving the definition essentially uninstructive.

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_inAppPurchases, and fields_inAppPurchaseImages fully. The description contributes no additional parameter semantics, which is the baseline 3 when the schema does all the work.

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 a restatement of the REST endpoint path, duplicated verbatim: "GET /v1/inAppPurchaseImages/{id} (GET /v1/inAppPurchaseImages/{id})". It adds nothing beyond the tool name in_app_purchase_images_get_instance, which already encodes the verb and resource, and it does not distinguish this from sibling retrievers like in_app_purchase_images_v2_get_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?

No when-to-use guidance, no exclusions, and no mention of alternatives. The GET path weakly implies a read of one image by ID, but nothing states when an agent should prefer this v1 endpoint over the v2 or relationship variants in the sibling list.

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