Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

beta_app_review_details__list

Read-onlyIdempotent

List beta app review details for your apps. Filter by app ID, include related records, select specific fields, and control pagination to retrieve only the data needed for review management.

Instructions

List beta app review details. [GET /v1/betaAppReviewDetails]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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_appYesfilter by id(s) of related 'app' The numeric Apple ID from apps__list, not the bundle ID. A bundle ID matches nothing and comes back as 200 with an empty list.
fields_betaAppReviewDetailsNothe fields to include for returned resources of type betaAppReviewDetails 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.2.0
    • changedInput schema / properties / filter_app / description
      Previous value: -"filter by id(s) of related 'app'"New value: +"filter by id(s) of related 'app' The numeric Apple ID from apps__list, not the bundle ID. A bundle ID matches nothing and comes back as 200 with an empty list."
  2. Changed3 schema fields changedv2.0.0
    • addedInput schema / properties / fields_betaAppReviewDetails
      Added value: +{
+  "description": "the fields to include for returned resources of type betaAppReviewDetails Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "contactFirstName",
+      "contactLastName",
+      "contactPhone",
+      "contactEmail",
+      "demoAccountName",
+      "demoAccountPassword",
+      "demoAccountRequired",
+      "notes",
+      "app"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • 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."
  3. First observedv1.3.0

TDQS

C2.8/5.0
Behavior3/5

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

The annotations (readOnlyHint, idempotentHint, destructiveHint) clearly indicate a safe, idempotent, read-only operation, so the bar for description is lower. The description does not contradict these annotations and correctly implies listing. It could add behavioral context about pagination or response size, but the annotations already convey the safety profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and to the point with two sentences. Every word earns its place, and the HTTP endpoint suffix is informative. It is front-loaded and no unnecessary elaboration.

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

Completeness2/5

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

Given the tool is a list operation with 5 parameters, no output schema, and many sibling tools that might be confused, the description is too sparse. It does not explain the return structure, pagination, or common pitfalls like the note about the bundle ID in the filter_app schema description being in the schema but not reiterated in the tool description.

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 description adds minimal extra meaning beyond the parameter names and their schema descriptions. It does not provide additional usage context or constraints beyond what is in the input schema.

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

Purpose3/5

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

The description states it lists beta app review details, but is generic and does not distinguish it from other similarly named tools like 'beta_app_review_details__get' or 'beta_app_review_details__update'. The appendage of the HTTP path is marginally helpful but does not provide a unique scope or verb-resource distinction.

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?

There is no guidance on when to use this list tool versus the singular 'get' or the 'update' counterpart. The description lacks any when-to-use or when-not-to-use instructions, and the filter_app parameter is described but not contextualized as a main filter requirement.

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