Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

app_clip_default_experience_localizations__get

Read-onlyIdempotent

Retrieve a specific App Clip default experience localization by ID, with optional inclusion of related records like the default experience or header image to reduce API calls.

Instructions

Read one App Clip default experience localization by ID. [GET /v1/appClipDefaultExperienceLocalizations/{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_appClipDefaultExperienceLocalizationsNothe fields to include for returned resources of type appClipDefaultExperienceLocalizations 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_appClipDefaultExperienceLocalizations
      Added value: +{
+  "description": "the fields to include for returned resources of type appClipDefaultExperienceLocalizations Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "locale",
+      "subtitle",
+      "appClipDefaultExperience",
+      "appClipHeaderImage"
+    ],
+    "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

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is established. The description adds the endpoint and confirms the read behavior, but does not provide extra details like authentication, rate limits, or return structure. Consistent with annotations, no contradiction.

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?

One concise sentence plus the endpoint. No wasted words, and the key information is front-loaded.

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 simple read tool with complete schema, annotations, and clear purpose, the description is sufficient. It does not explain the output format, but no output schema exists and the resource name implies it. Slight gap about response structure, but not essential.

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 each parameter (id, include, fields_...) having its own description. The tool description itself does not add parameter information, but the schema carries the burden. Baseline of 3 is appropriate.

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 a specific verb ('Read') with a precise resource ('App Clip default experience localization') and the method ('by ID'). It clearly distinguishes this from sibling create/update/delete operations and includes the endpoint for additional clarity.

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 implies the use case: fetching a single localization when you have its ID. It does not explicitly mention alternatives or when-not-to-use, but the context is clear enough for a simple read operation. No exclusions are stated, but none are needed.

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