Heimdall App Store Connect MCP

by erayendes

Overview Schema Source Related Servers Discussions Admin

TypeScript

apps__list

Read-onlyIdempotent

List all apps in an App Store Connect account to locate app IDs and review app details.

Instructions

List all apps in your App Store Connect account. Start here when you need an app ID. [GET /v1/apps]

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	comma-separated list of sort expressions; resources will be sorted as specified
`limit`	No	maximum resources per page
`include`	No	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.
`next_url`	No	Absolute links.next URL from a previous response.
`filter_id`	No	filter by id(s)
`filter_sku`	No	filter by attribute 'sku'
`fields_apps`	No	the fields to include for returned resources of type apps Return only these attributes. A full row set can exceed 200 KB.
`filter_name`	No	filter by attribute 'name'
`filter_bundleId`	No	filter by attribute 'bundleId'
`filter_appStoreVersions`	No	filter by id(s) of related 'appStoreVersions' Takes a 'appStoreVersions' resource id, read from the call that lists them — not a name. A value that matches nothing returns 200 with an empty list rather than an error.
`filter_reviewSubmissions.state`	No	filter by attribute 'reviewSubmissions.state'
`exists_gameCenterEnabledVersions`	No	filter by existence or non-existence of related 'gameCenterEnabledVersions'
`filter_appStoreVersions.platform`	No	filter by attribute 'appStoreVersions.platform'
`filter_reviewSubmissions.platform`	No	filter by attribute 'reviewSubmissions.platform'
`filter_appStoreVersions.appStoreState`	No	filter by attribute 'appStoreVersions.appStoreState'
`filter_appStoreVersions.appVersionState`	No	filter by attribute 'appStoreVersions.appVersionState'

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.4.2Sep 30, 2026

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"
+]

Changed1 schema field changedv2.2.0Aug 18, 2026

changedInput schema / properties / filter_appStoreVersions / description

Previous value: -"filter by id(s) of related 'appStoreVersions'"New value: +"filter by id(s) of related 'appStoreVersions' Takes a 'appStoreVersions' resource id, read from the call that lists them — not a name. A value that matches nothing returns 200 with an empty list rather than an error."

Changed3 schema fields changedv2.0.0Aug 5, 2026

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"
+}

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."

First observedv1.3.0Jul 28, 2026

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, covering the safety profile. The description adds only a workflow hint ('start here') and the underlying HTTP endpoint, disclosing nothing about pagination behavior or result shape. With annotations carrying the behavioral burden, a 3 is appropriate.

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 sentences plus an endpoint tag, with the core action front-loaded and the workflow cue second. Nothing is wasted.

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 read-only list tool whose schema fully documents filtering, field selection, inclusion and pagination, the description covers what an agent needs to call it correctly. It is slightly thin on how to page through results, though the next_url and limit parameters already handle that.

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 several parameter descriptions (include, fields_apps, filter_appStoreVersions, next_url) already add real operational guidance in the schema. The description itself adds no parameter semantics, 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?

States a specific verb+resource+scope: 'List all apps in your App Store Connect account.' This clearly distinguishes it from the singular sibling apps__get and other apps__* list tools. It stops short of naming an alternative, so it is clear but not sibling-differentiating in text.

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

Usage Guidelines4/5

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

'Start here when you need an app ID' gives an explicit condition for reaching for this tool, effectively framing it as the entry point that produces IDs needed by most other apps__* tools. No when-not or named alternative is given, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

apps__list

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools