Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

apps__app_infos__list

Read-onlyIdempotent

List app info records for an app by name, bundle ID, or numeric Apple ID, with optional related data like localizations and categories.

Instructions

List the app infos belonging to an app. [GET /v1/apps/{id}/appInfos]

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.
fields_appInfosNothe fields to include for returned resources of type appInfos 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_appInfos / items / enum
      Previous value: -[
-  "appStoreState",
-  "state",
-  "appStoreAgeRating",
-  "australiaAgeRating",
-  "brazilAgeRating",
-  "brazilAgeRatingV2",
-  "franceAgeRating",
-  "koreaAgeRating",
-  "kidsAgeBand",
-  "app",
-  "ageRatingDeclaration",
-  "appInfoLocalizations",
-  "primaryCategory",
-  "primarySubcategoryOne",
-  "primarySubcategoryTwo",
-  "secondaryCategory",
-  "secondarySubcategoryOne",
-  "secondarySubcategoryTwo",
-  "territoryAgeRatings"
-]New value: +[
+  "appStoreState",
+  "state",
+  "appStoreAgeRating",
+  "australiaAgeRating",
+  "brazilAgeRating",
+  "brazilAgeRatingV2",
+  "franceAgeRating",
+  "koreaAgeRating",
+  "app",
+  "ageRatingDeclaration",
+  "appInfoLocalizations",
+  "primaryCategory",
+  "primarySubcategoryOne",
+  "primarySubcategoryTwo",
+  "secondaryCategory",
+  "secondarySubcategoryOne",
+  "secondarySubcategoryTwo",
+  "territoryAgeRatings"
+]
  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. Changed4 schema fields changedv2.0.0
    • addedInput schema / properties / fields_appInfos
      Added value: +{
+  "description": "the fields to include for returned resources of type appInfos Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "appStoreState",
+      "state",
+      "appStoreAgeRating",
+      "australiaAgeRating",
+      "brazilAgeRating",
+      "brazilAgeRatingV2",
+      "franceAgeRating",
+      "koreaAgeRating",
+      "kidsAgeBand",
+      "app",
+      "ageRatingDeclaration",
+      "appInfoLocalizations",
+      "primaryCategory",
+      "primarySubcategoryOne",
+      "primarySubcategoryTwo",
+      "secondaryCategory",
+      "secondarySubcategoryOne",
+      "secondarySubcategoryTwo",
+      "territoryAgeRatings"
+    ],
+    "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."
  5. First observedv1.3.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered. The description adds only the REST route (GET /v1/apps/{id}/appInfos), with nothing about auth, rate limits, or pagination behavior; modest additional value over 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.

Conciseness4/5

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

A single front-loaded sentence plus the endpoint reference; both are short and there is no filler. It is efficient, though the endpoint tag adds little for an agent.

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 paginated list tool with five parameters and no output schema, the description omits pagination behavior and the shape/content of returned app infos, leaving that burden on the schema. Adequate but with clear gaps.

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%, including useful semantics for limit, include, next_url and fields_appInfos, so the baseline of 3 applies. The description contributes no parameter meaning of its own.

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 gives a specific verb and resource ('List the app infos belonging to an app') and even names the underlying endpoint, so an agent knows exactly what it retrieves. It stops short of explicitly contrasting itself with the sibling app_infos__get, but list-vs-get is strongly implied.

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?

There is no statement of when to use this versus app_infos__get or the other app_infos__* sub-resource list tools, and no prerequisites or exclusions. The agent must infer usage entirely from the name.

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