Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

apps__app_infos__list

Read-onlyIdempotent

List app infos for any app by providing its name, bundle ID, or Apple ID. Supports pagination and relationship inclusion to fetch detailed app metadata.

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.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_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."
  4. First observedv1.3.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destuctiveHint=false, and the description ('List') is fully consistent with them — no contradiction. However, the description adds no behavioral context beyond that scope: no pagination behavior, rate limits, auth requirements, or response-size consequences (the 200 KB warning lives in the schema, not the description).

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 with zero filler; the verb+resource is front-loaded before the endpoint reference. Every word earns its place, and the endpoint adds useful confirmation of the operation without redundancy.

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 5-parameter list tool with rich schema descriptions and safety annotations, the definition is adequate. Gaps remain: pagination is only cryptically hinted at via limit/next_url parameter descriptions, and there is no guidance for choosing this tool over app_infos__get. The absence of an output schema is partially mitigated by the description naming the returned resource type.

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 even without parameter info in the description. The description itself says nothing about id, limit, include, next_url, or fields_appInfos; the schema carries all parameter semantics, including enum options and the extra-call cost of omitted includes.

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') and resource ('app infos belonging to an app'), making the function immediately clear, and the endpoint reference reinforces the resource hierarchy. It does not explicitly name or contrast sibling tools, but the list-versus-get distinction against app_infos__get is evident from the verb and naming convention.

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?

The description provides no guidance on when to use this tool versus app_infos__get (single record), app_infos__update, or app_infos__age_rating_declaration-style sibling routes. No exclusions are stated and no alternatives are mentioned, so an agent must infer usage from the tool name and endpoint pattern.

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