Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

app_clip_advanced_experience_images__get

Read-onlyIdempotent

Retrieve a specific App Clip advanced experience image by ID to access its file details, asset state, and upload operations from App Store Connect.

Instructions

Read one App Clip advanced experience image by ID. [GET /v1/appClipAdvancedExperienceImages/{id}]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID from the matching list call.
fields_appClipAdvancedExperienceImagesNothe fields to include for returned resources of type appClipAdvancedExperienceImages 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. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / fields_appClipAdvancedExperienceImages
      Added value: +{
+  "description": "the fields to include for returned resources of type appClipAdvancedExperienceImages Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "fileSize",
+      "fileName",
+      "sourceFileChecksum",
+      "imageAsset",
+      "uploadOperations",
+      "assetDeliveryState"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / id / description
      Removed value: -"Resource identifier."
  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, and destructiveHint=false. The description adds no additional behavioral context such as response size, rate limits, or default field behavior, merely restating the read operation.

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?

Single sentence plus endpoint reference; extremely concise and front-loaded with no redundant information.

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 tool is a simple read with complete schema and annotation coverage. The description lacks explanation of default return fields, but annotations and schema compensate sufficiently for this low-complexity operation.

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 input schema fully documents both parameters (id with 'ID from the matching list call' and fields with a clear description), so the description need not add more. Schema coverage is 100%, placing this at baseline 3.

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?

Description states 'Read one App Clip advanced experience image by ID' with a specific verb and resource, clearly distinguishing it from sibling create/update operations for the same resource. The endpoint is also included for technical clarity.

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 implicitly clear (fetch a single image by ID), but no explicit when-to-use guidance or comparisons to alternatives (e.g., list or update tools) are provided in the description.

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