Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

app_store_version_localizations__get

Read-onlyIdempotent

Retrieve a single App Store version localization by ID to inspect its details, optionally including related sets and specifying fields to limit response size.

Instructions

Read one App Store version localization by ID. [GET /v1/appStoreVersionLocalizations/{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_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. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / id / description
      Added value: +"ID from the matching list call."
  2. 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."
  3. First observedv1.3.0

TDQS

A3.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is known. The description adds no additional context about response behavior, auth requirements, or side effects; it merely restates that it reads a resource. No contradiction exists, but no extra value is contributed.

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?

The description is two sentences: one clear purpose statement and one endpoint reference. Both are concise and front-loaded, with no redundancy or filler.

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?

The description clearly identifies what the tool does and what it returns (the localization object). It does not explain the optional include/fields behavior, but that is fully documented in the schema. Given the read-only annotations and straightforward single-resource get, the description is sufficiently complete, though a bit more context about the include parameter could improve it.

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% with detailed descriptions for id and optional include/fields parameters. The tool description itself does not mention parameters or add semantics beyond what the schema provides, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb 'Read' and a specific resource 'one App Store version localization by ID.' It distinguishes from sibling tools like app_store_version_localizations__update, __delete, and list operations. The HTTP endpoint reinforces the resource identity.

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 description implies usage for retrieving a single localization by ID, but does not explicitly state when to use this tool vs alternatives like listing localizations or using variant tools. No exclusions or alternative recommendations are given.

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