Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

customer_reviews__get

Read-onlyIdempotent

Retrieve a specific customer review by its ID, including optional related records like your response or review territory. Pull only the fields you need to minimize data transfer.

Instructions

Read one customer review by ID. [GET /v1/customerReviews/{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_customerReviewsNothe fields to include for returned resources of type customerReviews 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_customerReviews
      Added value: +{
+  "description": "the fields to include for returned resources of type customerReviews Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "rating",
+      "title",
+      "body",
+      "reviewerNickname",
+      "createdDate",
+      "territory",
+      "response",
+      "reviewTerritory"
+    ],
+    "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

B3.1/5.0
Behavior2/5

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

The annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) already disclose the safety profile, so the bar is lower. However, the description adds no extra behavioral context, such as pagination, return shape, or relationship handling. It simply restates the operation name.

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, focused sentence plus the endpoint. It is front-loaded with the verb and resource, contains zero filler, and is appropriately sized for a simple get-by-id tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

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

Given the simplicity of the tool and full schema coverage, the description is minimally viable. However, it does not mention what the return value contains, and there is no output schema. The fields_customerReviews enum provides some insight into possible attributes, but the description itself is thin.

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%, so the baseline is 3. The top-level description adds no parameter semantics beyond what the schema already provides, but the schema adequately documents 'id', 'include', and 'fields_customerReviews' with useful examples and limitations.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Read one customer review') and scope ('by ID'), which is specific and unambiguous. It distinguishes from list operations by using 'one' and 'by ID', though it does not explicitly mention sibling tools like customer_reviews__response__get.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention that the ID should come from a list call, nor does it distinguish this from other review-related tools. The parameter hint 'ID from the matching list call' appears in the schema but not 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