Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

apps__get

Read-onlyIdempotent

Retrieve one app from App Store Connect by ID to view its bundle ID, SKU, and primary locale. Optionally include related records in the same request.

Instructions

Read one app by ID, including bundle ID, SKU and primary locale. [GET /v1/apps/{id}]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesApp name, bundle ID (com.example.app) or numeric Apple ID.
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.
fields_appsNothe fields to include for returned resources of type apps 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.4.2
    • changedInput schema / properties / fields_apps / items / enum
      Previous value: -[
-  "accessibilityUrl",
-  "name",
-  "bundleId",
-  "sku",
-  "primaryLocale",
-  "isOrEverWasMadeForKids",
-  "subscriptionStatusUrl",
-  "subscriptionStatusUrlVersion",
-  "subscriptionStatusUrlForSandbox",
-  "subscriptionStatusUrlVersionForSandbox",
-  "contentRightsDeclaration",
-  "streamlinedPurchasingEnabled",
-  "accessibilityDeclarations",
-  "appEncryptionDeclarations",
-  "appStoreIcon",
-  "ciProduct",
-  "betaTesters",
-  "betaGroups",
-  "appStoreVersions",
-  "appTags",
-  "preReleaseVersions",
-  "betaAppLocalizations",
-  "builds",
-  "betaLicenseAgreement",
-  "betaAppReviewDetail",
-  "appInfos",
-  "appClips",
-  "appPricePoints",
-  "endUserLicenseAgreement",
-  "appPriceSchedule",
-  "appAvailabilityV2",
-  "inAppPurchases",
-  "subscriptionGroups",
-  "gameCenterEnabledVersions",
-  "perfPowerMetrics",
-  "appCustomProductPages",
-  "inAppPurchasesV2",
-  "promotedPurchases",
-  "appEvents",
-  "reviewSubmissions"
-]New value: +[
+  "accessibilityUrl",
+  "name",
+  "bundleId",
+  "sku",
+  "primaryLocale",
+  "isOrEverWasMadeForKids",
+  "subscriptionStatusUrl",
+  "subscriptionStatusUrlVersion",
+  "subscriptionStatusUrlForSandbox",
+  "subscriptionStatusUrlVersionForSandbox",
+  "contentRightsDeclaration",
+  "streamlinedPurchasingEnabled",
+  "accessibilityDeclarations",
+  "appEncryptionDeclarations",
+  "appStoreIcon",
+  "ciProduct",
+  "betaTesters",
+  "betaGroups",
+  "appStoreVersions",
+  "appTags",
+  "preReleaseVersions",
+  "betaAppLocalizations",
+  "builds",
+  "betaLicenseAgreement",
+  "betaAppReviewDetail",
+  "appInfos",
+  "appClips",
+  "appPricePoints",
+  "endUserLicenseAgreement",
+  "appPriceSchedule",
+  "appAvailabilityV2",
+  "inAppPurchases",
+  "subscriptionGroups",
+  "gameCenterEnabledVersions",
+  "performanceOverviews",
+  "perfPowerMetrics",
+  "appCustomProductPages",
+  "inAppPurchasesV2",
+  "promotedPurchases",
+  "appEvents"
+]
  2. 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."
  3. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / id / description
      Added value: +"ID from the matching list call."
  4. Changed3 schema fields changedv2.0.0
    • addedInput schema / properties / fields_apps
      Added value: +{
+  "description": "the fields to include for returned resources of type apps Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "accessibilityUrl",
+      "name",
+      "bundleId",
+      "sku",
+      "primaryLocale",
+      "isOrEverWasMadeForKids",
+      "subscriptionStatusUrl",
+      "subscriptionStatusUrlVersion",
+      "subscriptionStatusUrlForSandbox",
+      "subscriptionStatusUrlVersionForSandbox",
+      "contentRightsDeclaration",
+      "streamlinedPurchasingEnabled",
+      "accessibilityDeclarations",
+      "appEncryptionDeclarations",
+      "appStoreIcon",
+      "ciProduct",
+      "betaTesters",
+      "betaGroups",
+      "appStoreVersions",
+      "appTags",
+      "preReleaseVersions",
+      "betaAppLocalizations",
+      "builds",
+      "betaLicenseAgreement",
+      "betaAppReviewDetail",
+      "appInfos",
+      "appClips",
+      "appPricePoints",
+      "endUserLicenseAgreement",
+      "appPriceSchedule",
+      "appAvailabilityV2",
+      "inAppPurchases",
+      "subscriptionGroups",
+      "gameCenterEnabledVersions",
+      "perfPowerMetrics",
+      "appCustomProductPages",
+      "inAppPurchasesV2",
+      "promotedPurchases",
+      "appEvents",
+      "reviewSubmissions"
+    ],
+    "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."
  5. 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, destructiveHint=false, so the read-only safety profile is covered structurally. The description is consistent with that but adds little beyond a restatement of the read intent plus the raw endpoint; it omits any note on sparse fields, expansion cost, or response size (the schema itself flags a >200 KB row set).

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 short clauses: the action first, then the endpoint reference. No padding, and the core purpose is front-loaded.

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?

With no output schema, the description does briefly enumerate the salient returned fields, which is useful. Annotations cover the safety profile, and the schema covers parameters, so little is missing; it could go slightly further on how sparse fieldsets affect the response, but it is largely complete for a simple read.

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 id, include, and fields_apps parameters are already fully documented in the schema, including the enum options and their cost trade-offs. The description only echoes the id lookup, adding no new semantic detail, which is the expected baseline of 3 when the schema does the heavy lifting.

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?

The description states a specific verb+resource ('Read one app by ID') and scopes it to a single record, which cleanly separates it from the sibling apps__list. The additional detail on returned fields (bundle ID, SKU, primary locale) reinforces what 'get' means here.

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?

It implies usage by saying 'by ID' and noting the returned identifiers, but never states when to prefer this over apps__list or the related apps__app_infos__list / app_infos__get siblings. No explicit exclusions or alternatives are given, so the guidance is only inferred.

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