Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

app_clip_app_store_review_details__get

Read-onlyIdempotent

Fetch App Clip App Store review details by ID. Include related appClipDefaultExperience or specific fields to get targeted data in one call.

Instructions

Read one App Clip App Store review detail by ID. [GET /v1/appClipAppStoreReviewDetails/{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_appClipAppStoreReviewDetailsNothe fields to include for returned resources of type appClipAppStoreReviewDetails 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_appClipAppStoreReviewDetails
      Added value: +{
+  "description": "the fields to include for returned resources of type appClipAppStoreReviewDetails Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "invocationUrls",
+      "appClipDefaultExperience"
+    ],
+    "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
Behavior3/5

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

The annotations already declare readOnlyHint=true and idempotentHint=true, and the description's 'Read' aligns with those. However, the description adds no extra behavioral context such as error handling, availability, or relationship behavior beyond what annotations and schema already convey.

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 a single concise sentence that front-loads the verb and resource, followed by the endpoint path. It contains no filler or redundant information, earning top marks for structure.

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-by-ID operation with rich schema annotations and full parameter descriptions, the description is functionally sufficient. However, it omits any mention of optional relationship inclusion or what the response contains, though the schema partially compensates. Still, given the annotations and schema, the description is nearly complete for this tool's complexity.

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 has 100% description coverage, with each parameter (id, include, fields_...) having explicit descriptions. The tool description only mentions 'by ID,' but the schema already explains the ID source and optional parameters, so the description adds no additional semantic value.

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 specifies the verb 'Read' and the resource 'App Clip App Store review detail' with an ID input, clearly indicating this is a single-item get operation. It distinguishes itself from sibling create/update/delete tools and includes the HTTP 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 Guidelines2/5

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

The description provides no guidance on when to choose this tool over alternatives, nor does it mention the prerequisite that the ID comes from a prior list call (though the schema does). It only states what the tool does, so an agent must infer usage from the name and schema.

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