Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

apps__customer_review_summarizations__list

Read-onlyIdempotent

Fetch customer review summarizations for a specific app. Filter results by platform, territory, and include related records to analyze review feedback efficiently.

Instructions

List the customer review summarizations belonging to an app. [GET /v1/apps/{id}/customerReviewSummarizations]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesApp name, bundle ID (com.example.app) or numeric Apple ID.
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_platformYesfilter by attribute 'platform'
filter_territoryNofilter by id(s) of related '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_customerReviewSummarizationsNothe fields to include for returned resources of type customerReviewSummarizations 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.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. Changed5 schema fields changedv2.0.0
    • addedInput schema / properties / fields_customerReviewSummarizations
      Added value: +{
+  "description": "the fields to include for returned resources of type customerReviewSummarizations Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "createdDate",
+      "locale",
+      "platform",
+      "text",
+      "territory"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / filter_territory / description
      Previous value: -"filter by id(s) of related 'territory'"New value: +"filter by id(s) of related '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

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is established. The description adds only the app-scoping constraint and the GET endpoint; it does not disclose pagination or response defaults, but that information is largely carried by the schema. 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?

One sentence with the endpoint suffix, no filler. The core action and scope are front-loaded.

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-only list with fully documented parameters and strong annotations, and the description gives the essential app-scoped context. No output schema exists, but the fields_customerReviewSummarizations enum and resource name make the return shape inferable. It is adequate without being exhaustive.

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 and the schema already documents all seven parameters. The description adds no parameter detail, but none is needed given the rich per-field descriptions.

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 names a specific verb ('List'), a concrete resource ('customer review summarizations'), and the scope ('belonging to an app'). This clearly distinguishes it from sibling review-related list tools such as apps__customer_reviews__list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The 'belonging to an app' phrasing gives clear context that this endpoint is for app-scoped summarizations and that the caller must supply an app identifier. It does not name alternatives or state when not to use it, but the resource scope is unambiguous.

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