Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

apps__pre_release_versions__list

Read-onlyIdempotent

List pre-release versions for an app by name, bundle ID, or Apple ID. Paginate and select fields via query parameters.

Instructions

List the pre release versions belonging to an app. [GET /v1/apps/{id}/preReleaseVersions]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesApp name, bundle ID (com.example.app) or numeric Apple ID.
limitNomaximum resources per page
next_urlNoAbsolute links.next URL from a previous response.
fields_preReleaseVersionsNothe fields to include for returned resources of type preReleaseVersions 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. Changed3 schema fields changedv2.0.0
    • addedInput schema / properties / fields_preReleaseVersions
      Added value: +{
+  "description": "the fields to include for returned resources of type preReleaseVersions Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "version",
+      "platform",
+      "builds",
+      "app"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / id / description
      Removed value: -"Resource identifier."
    • 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

B3.3/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, so the safety profile is fully covered. The description's 'List' verb and '[GET ...]' endpoint are consistent with these annotations and add the app-scoping detail, but it discloses no further behavioral context such as pagination behavior or large response sizes (which the schema hints at via the 200 KB note on the fields parameter). No contradiction exists.

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?

A single sentence followed by the endpoint reference with zero filler or redundancy. The action is front-loaded, and the definition is appropriately sized given that the schema and annotations already carry the parameter and safety details.

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

Completeness3/5

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

For a read-only, idempotent list endpoint whose parameters are fully documented in the schema, the definition is nearly sufficient. The real gap is that the similarly named sibling pre_release_versions__list exists with no stated distinction, and since there is no output schema, the description gives no hint about the response shape. It is minimally viable but leaves sibling ambiguity unresolved.

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 the schema richly documents all four parameters: id accepts 'App name, bundle ID (com.example.app) or numeric Apple ID', limit is 'maximum resources per page', next_url is a pagination link, and fields_preReleaseVersions has an enum plus a 200 KB row-size warning. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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

Purpose4/5

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

The description states a specific verb ('List'), a specific resource ('pre release versions'), and a scoping qualifier ('belonging to an app'), reinforced by the endpoint path [GET /v1/apps/{id}/preReleaseVersions]. It is clear about what the tool does, but it does not explicitly differentiate itself from the nearly identical sibling pre_release_versions__list.

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 guidance is given about when to use this tool versus alternatives. The sibling set contains several overlapping tools (pre_release_versions__list, pre_release_versions__get, pre_release_versions__app__get, pre_release_versions__builds__list), yet the description names none of them and provides no exclusion conditions or selection criteria.

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