Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

apps__app_store_versions__list

Read-onlyIdempotent

List App Store versions for an app and view each version's review state to track submission progress, filter by platform or state.

Instructions

List App Store versions for an app, with their review state (e.g. PREPARE_FOR_SUBMISSION, WAITING_FOR_REVIEW, READY_FOR_SALE). [GET /v1/apps/{id}/appStoreVersions]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesApp name, bundle ID (com.example.app) or numeric Apple ID.
limitNomaximum resources per page
includeNocomma-separated list of relationships to include Pull related records in the same call. Without it, checking a relationship costs one extra call per row returned.
next_urlNoAbsolute links.next URL from a previous response.
filter_idNofilter by id(s)
filter_platformNofilter by attribute 'platform'
filter_appStoreStateNofilter by attribute 'appStoreState'
filter_versionStringNofilter by attribute 'versionString'
filter_appVersionStateNofilter by attribute 'appVersionState'
fields_appStoreVersionsNothe fields to include for returned resources of type appStoreVersions Return only these attributes. A full row set can exceed 200 KB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.0
    • changedInput schema / properties / id / description
      Previous value: -"ID from the matching list call."New value: +"App name, bundle ID (com.example.app) or numeric Apple ID."
  2. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / id / description
      Added value: +"ID from the matching list call."
  3. Changed4 schema fields changedv2.0.0
    • addedInput schema / properties / fields_appStoreVersions
      Added value: +{
+  "description": "the fields to include for returned resources of type appStoreVersions Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "platform",
+      "versionString",
+      "appStoreState",
+      "appVersionState",
+      "copyright",
+      "reviewType",
+      "releaseType",
+      "earliestReleaseDate",
+      "usesIdfa",
+      "downloadable",
+      "createdDate",
+      "app",
+      "appStoreVersionLocalizations",
+      "build",
+      "appStoreVersionPhasedRelease",
+      "gameCenterAppVersion",
+      "routingAppCoverage",
+      "appStoreReviewDetail",
+      "appStoreVersionSubmission",
+      "appClipDefaultExperience",
+      "appStoreVersionExperiments",
+      "appStoreVersionExperimentsV2",
+      "customerReviews",
+      "alternativeDistributionPackage"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / id / description
      Removed value: -"Resource identifier."
    • changedInput schema / properties / include / description
      Previous value: -"comma-separated list of relationships to include"New value: +"comma-separated list of relationships to include Pull related records in the same call. Without it, checking a relationship costs one extra call per row returned."
    • changedInput schema / properties / next_url / description
      Previous value: -"Absolute `links.next` URL from a previous response, to fetch the next page. When set, all other parameters are ignored."New value: +"Absolute links.next URL from a previous response."
  4. First observedv1.3.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the 'List' semantics match that profile with no contradiction. The description adds the review-state context but does not disclose pagination behavior (despite limit/next_url in the schema), auth requirements, or what happens for invalid app IDs, so it adds only modest value beyond the annotations.

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

Conciseness5/5

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

Two sentences with zero filler: action, resource, distinguishing output, then endpoint reference. The core behavior is front-loaded and every clause earns its place.

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

Completeness4/5

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

For a list tool whose safety profile is fully covered by annotations and whose 10 parameters are 100% documented in the schema, the description is nearly sufficient. The main gap is behavioral context such as pagination defaults or the cost implications of the include parameter, though schema documentation partially mitigates these; an explicit note about pagination would make it complete.

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 baseline is 3. The description adds slight value by exemplifying filter values (PREPARE_FOR_SUBMISSION, WAITING_FOR_REVIEW, READY_FOR_SALE) that correspond to filter_appStoreState/filter_appVersionState, but the schema already documents all parameter meanings including the id flexibility (name, bundle ID, or Apple ID).

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

Purpose5/5

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

States a specific verb ('List') with a clear resource ('App Store versions') scoped to an app via the endpoint path [GET /v1/apps/{id}/appStoreVersions]. The review-state detail (PREPARE_FOR_SUBMISSION, WAITING_FOR_REVIEW, READY_FOR_SALE) adds a distinguishing output feature that separates it from single-resource siblings like app_store_versions__get or mutation tools like app_store_versions__create.

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

Usage Guidelines3/5

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

The 'List' verb and collection endpoint imply this is for enumerating versions rather than fetching one or mutating one, but no explicit when-to-use guidance or alternative routing is provided. An agent must infer usage from the verb and endpoint rather than being told when to prefer this over siblings like app_store_versions__get or apps__builds__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