Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

app_infos__app_info_localizations__list

Read-onlyIdempotent

Retrieve localized metadata like name, subtitle, and privacy URLs for an app info by specifying its ID. Filter by locale and include related app info records to streamline App Store Connect data management.

Instructions

List the app info localizations belonging to an app info. [GET /v1/appInfos/{id}/appInfoLocalizations]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID from the matching list call.
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.
filter_localeNofilter by attribute 'locale'
fields_appInfoLocalizationsNothe fields to include for returned resources of type appInfoLocalizations 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. Changed4 schema fields changedv2.0.0
    • addedInput schema / properties / fields_appInfoLocalizations
      Added value: +{
+  "description": "the fields to include for returned resources of type appInfoLocalizations Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "locale",
+      "name",
+      "subtitle",
+      "privacyPolicyUrl",
+      "privacyChoicesUrl",
+      "privacyPolicyText",
+      "appInfo"
+    ],
+    "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."
  3. First observedv1.3.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds the relationship scope and endpoint, but does not disclose pagination behavior or response format. This is adequate but not rich, matching the baseline for annotation-covered tools.

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, front-loads the action, and includes the HTTP endpoint for reference. Every word earns its place, 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?

For a read-only list tool with full parameter descriptions and safety annotations, the description is largely sufficient. It clearly states what is being listed and the parent resource. It does not detail the response shape or pagination, but those are inferable from the name and purpose; the absence of an output schema makes this a minor gap.

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% for all 6 parameters, so the baseline is 3. The description adds no additional meaning beyond the schema; it only restates the relationship that the 'id' parameter is for an app info, which is already implied by the schema description.

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 uses the verb 'List' and specifies the resource 'app info localizations belonging to an app info,' clearly identifying it as a collection retrieval scoped to an app info. It is easily distinguished from sibling tools like app_info_localizations__get (single get) and app_infos__get (app info itself).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context: it lists localizations that belong to an app info, implying the need for an app info ID. It does not explicitly mention alternatives or exclusions, but the scope is unambiguous enough for an agent to know when to use this tool versus other list tools.

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