Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

app_infos__get

Read-onlyIdempotent

Fetch a single App Store Connect app info record by ID, optionally including related localizations, categories, and age ratings to avoid extra API calls.

Instructions

Read one app info by ID. [GET /v1/appInfos/{id}]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID from the matching list call.
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_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.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_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."
  4. First observedv1.3.0

TDQS

A3.5/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 covered. The description adds only the underlying endpoint '[GET /v1/appInfos/{id}]', which is mildly useful context but discloses no richer behavioral traits (e.g., pagination, sparse-field behavior, auth scope).

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 compact segments, front-loading the core action before the endpoint annotation. Every word earns its place with no 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?

With no output schema and quiet annotations, the description is thin: it says nothing about what the response contains or how sparse fields affect it. It is minimally adequate to invoke the tool but leaves return-value expectations to be inferred.

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 entries are genuinely informative (explaining that 'include' saves extra calls and 'fields_appInfos' avoids >200 KB rows). The description adds nothing beyond the schema, so the baseline 3 for fully-documented parameters is appropriate.

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 clear verb+resource: 'Read one app info by ID', which distinguishes it from the sibling list tool apps__app_infos__list and the mutation app_infos__update. It lacks explicit sibling differentiation (e.g., naming apps__app_infos__list), but the singular 'one app info by ID' scope is unambiguous.

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?

The schema's id description ('ID from the matching list call') implies you obtain the ID from the corresponding list call, giving weakly implied guidance. There is no explicit when-to-use statement, no mention of alternatives, and no prerequisites in the description itself.

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