Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

app_clip_default_experiences__get

Read-onlyIdempotent

Retrieve a specific App Clip default experience by ID, optionally including related App Clip, release, localizations, and review details. Fetches data with a single API call.

Instructions

Read one App Clip default experience by ID. [GET /v1/appClipDefaultExperiences/{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_appClipDefaultExperiencesNothe fields to include for returned resources of type appClipDefaultExperiences 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_appClipDefaultExperiences
      Added value: +{
+  "description": "the fields to include for returned resources of type appClipDefaultExperiences Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "action",
+      "appClip",
+      "releaseWithAppStoreVersion",
+      "appClipDefaultExperienceLocalizations",
+      "appClipAppStoreReviewDetail"
+    ],
+    "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.8/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 fully covered. The description's 'Read' aligns with these hints but adds no additional behavioral context such as pagination, rate limits, or error conditions. With annotations present, this is adequate.

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 short sentences, leading with the action and resource, followed by the endpoint. 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.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read operation with read-only annotations and a well-described schema, the description is adequate. It doesn't describe return values, but the resource name and endpoint make it clear. It omits any caveats, but given the tool's simplicity, it is sufficient.

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?

The schema provides 100% coverage with descriptions for all three parameters (id, include, fields_appClipDefaultExperiences), so the description does not need to explain them. The description itself adds no parameter-level details, but the schema already handles it.

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 clearly states 'Read one App Clip default experience by ID' with a specific verb and resource, distinguishing it from sibling tools that create, update, delete, or list. The HTTP endpoint reinforces the exact operation.

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 App Clip default experience by ID, but it does not explicitly state when to use this tool versus alternatives (e.g., list endpoints) or any prerequisites beyond the ID. No exclusions or alternative tools mentioned.

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