Skip to main content
Glama
Sign In
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

app_store_version_localizations__get

Read-onlyIdempotent

Fetch one App Store version localization by ID to read localized app metadata. Include related records or select specific fields in the same call.

Instructions

Read one App Store version localization by ID. [GET /v1/appStoreVersionLocalizations/{id}]

Input 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_appStoreVersionLocalizationsNothe fields to include for returned resources of type appStoreVersionLocalizations Return only these attributes. A full row set can exceed 200 KB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.8.0
    • changedInput schema / properties / fields_appStoreVersionLocalizations / items / enum
      Previous value: -[
-  "description",
-  "locale",
-  "keywords",
-  "marketingUrl",
-  "promotionalText",
-  "supportUrl",
-  "whatsNew",
-  "appStoreVersion",
-  "appScreenshotSets",
-  "appPreviewSets",
-  "searchKeywords"
-]New value: +[
+  "description",
+  "locale",
+  "keywords",
+  "marketingUrl",
+  "promotionalText",
+  "supportUrl",
+  "whatsNew",
+  "appStoreVersion",
+  "appScreenshotSets",
+  "appPreviewSets",
+  "searchKeywords",
+  "placements"
+]
    • changedInput schema / properties / include / items / enum
      Previous value: -[
-  "appStoreVersion",
-  "appScreenshotSets",
-  "appPreviewSets",
-  "searchKeywords"
-]New value: +[
+  "appStoreVersion",
+  "appScreenshotSets",
+  "appPreviewSets",
+  "searchKeywords",
+  "placements"
+]
  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_appStoreVersionLocalizations
      Added value: +{
+  "description": "the fields to include for returned resources of type appStoreVersionLocalizations Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "description",
+      "locale",
+      "keywords",
+      "marketingUrl",
+      "promotionalText",
+      "supportUrl",
+      "whatsNew",
+      "appStoreVersion",
+      "appScreenshotSets",
+      "appPreviewSets",
+      "searchKeywords"
+    ],
+    "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?

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered without the description. The description confirms single-entity read semantics but adds no extra context such as permission requirements, error behavior on unknown IDs, or the fact that relationship data must be requested via include.

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?

Two short sentences, front-loaded with the operation and resource; the bracketed GET path is genuinely useful for mapping to the underlying API rather than filler. Nothing extraneous, though nothing beyond the minimum was attempted either.

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 single-record fetch with complete schema descriptions and safety annotations, the definition supplies everything needed to invoke it correctly; no output schema exists but the return type (one localization with the enumerated fields) is inferable from the fields enum.

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 all three parameters (id, include, fields_appStoreVersionLocalizations) are already well documented, including the cost tradeoff of omitting include. The description contributes no additional parameter meaning, which matches the baseline for a fully documented schema.

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 and resource with singular scope ('Read one App Store version localization by ID'), which cleanly separates it from app_store_version_localizations__list and __create. It stops short of naming any sibling explicitly, so it is clear but not fully differentiated.

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?

Usage is only implied — the 'by ID' framing and the schema note 'ID from the matching list call' hint that a list call precedes this one, but the description itself states no when-to-use, no prerequisites, and no alternative for fetching many localizations at once.

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