Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

apps__customer_reviews__list

Read-onlyIdempotent

Retrieve customer reviews for an app, filter by rating or territory, and sort by newest creation date to analyze user feedback.

Instructions

List customer reviews for an app. Filter by rating or territory; sort by -createdDate for the newest. [GET /v1/apps/{id}/customerReviews]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesApp name, bundle ID (com.example.app) or numeric Apple ID.
sortNocomma-separated list of sort expressions; resources will be sorted as specified
limitNomaximum resources per page
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.
next_urlNoAbsolute links.next URL from a previous response.
filter_ratingNofilter by attribute 'rating'
filter_territoryNofilter by attribute 'territory' Three-letter ISO-3166 alpha-3 code — USA, TUR, DEU, GBR. Not the two-letter form: "US" is accepted and silently returns an empty list.
fields_customerReviewsNothe fields to include for returned resources of type customerReviews Return only these attributes. A full row set can exceed 200 KB.
filter_reviewTerritoryNofilter by id(s) of related 'reviewTerritory' Three-letter ISO-3166 alpha-3 code — USA, TUR, DEU, GBR. Not the two-letter form: "US" is accepted and silently returns an empty list.
exists_publishedResponseNofilter by publishedResponse

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.0
    • changedInput schema / properties / id / description
      Previous value: -"ID from the matching list call."New value: +"App name, bundle ID (com.example.app) or numeric Apple ID."
  2. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / id / description
      Added value: +"ID from the matching list call."
  3. Changed6 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"
+}
    • changedInput schema / properties / filter_reviewTerritory / description
      Previous value: -"filter by id(s) of related 'reviewTerritory'"New value: +"filter by id(s) of related 'reviewTerritory' Three-letter ISO-3166 alpha-3 code — USA, TUR, DEU, GBR. Not the two-letter form: \"US\" is accepted and silently returns an empty list."
    • changedInput schema / properties / filter_territory / description
      Previous value: -"filter by attribute 'territory'"New value: +"filter by attribute 'territory' Three-letter ISO-3166 alpha-3 code — USA, TUR, DEU, GBR. Not the two-letter form: \"US\" is accepted and silently returns an empty list."
    • 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."
    • changedInput schema / properties / next_url / description
      Previous value: -"Absolute `links.next` URL from a previous response, to fetch the next page. When set, all other parameters are ignored."New value: +"Absolute links.next URL from a previous response."
  4. First observedv1.3.0

TDQS

B3.4/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 covered. The description adds useful context like the REST endpoint and that '-createdDate' returns the newest reviews, but it does not disclose pagination, default fields, or payload size considerations. No contradiction with annotations.

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 front-loaded sentence followed by the endpoint. It communicates the core action, key filters, and sort intent with no filler or 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?

For a read-only list operation with 100% schema coverage and safe annotations, the description is nearly sufficient. It could mention pagination via `next_url` or the related `app_store_versions__customer_reviews__list` sibling, but the schema and annotations fill most gaps.

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 schema already documents all 10 parameters. The description adds only a high-level summary of filtering by rating/territory and sorting by newest, which is helpful but does not materially expand on the schema's detailed field descriptions.

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 uses a specific verb and resource: 'List customer reviews for an app.' It also names the endpoint, which clarifies the operation. It does not explicitly differentiate from the similar sibling `app_store_versions__customer_reviews__list`, so it stops short of a 5.

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 gives filter and sort guidance but no explicit when-to-use guidance or alternative exclusions. Given the existence of `app_store_versions__customer_reviews__list` and `customer_reviews__get`, the agent gets no help choosing among related review-listing tools.

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