Skip to main content
Glama
Sign In
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

review_submissions__items__list

Read-onlyIdempotent

List review submission items and their states to confirm what Apple will review before submitting.

Instructions

List what is inside a review submission and the state of each item, so you can check what Apple will actually look at before handing it over. [GET /v1/reviewSubmissions/{id}/items]

Input Schema

NameRequiredDescriptionDefault
idYesID from the matching list call.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.8.0
    • changedInput schema / properties / include / items / enum
      Previous value: -[
-  "appStoreVersion",
-  "appCustomProductPageVersion",
-  "appStoreVersionExperiment",
-  "appStoreVersionExperimentV2",
-  "appEvent",
-  "backgroundAssetVersion",
-  "gameCenterAchievementVersion",
-  "gameCenterActivityVersion",
-  "gameCenterChallengeVersion",
-  "gameCenterLeaderboardSetVersion",
-  "gameCenterLeaderboardVersion",
-  "inAppPurchaseVersion",
-  "subscriptionVersion",
-  "subscriptionGroupVersion"
-]New value: +[
+  "appStoreVersion",
+  "appCustomProductPageVersion",
+  "appStoreVersionExperiment",
+  "appStoreVersionExperimentV2",
+  "appEvent",
+  "appAssetLibraryImage",
+  "appAssetLibraryVideo",
+  "backgroundAssetVersion",
+  "gameCenterAchievementVersion",
+  "gameCenterActivityVersion",
+  "gameCenterChallengeVersion",
+  "gameCenterLeaderboardSetVersion",
+  "gameCenterLeaderboardVersion",
+  "inAppPurchaseVersion",
+  "subscriptionVersion",
+  "subscriptionGroupVersion"
+]
  2. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / id / description
      Added value: +"ID from the matching list call."
  3. Changed3 schema fields changedv2.0.0
    • 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?

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the pre-handover inspection purpose but does not explain pagination, response shape, or the include parameter's extra-call cost beyond what the schema already documents.

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 plus the endpoint path, with no wasted wording. It immediately conveys the operation and why an agent would call it.

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 listing tool with full schema descriptions and safety annotations, the description is largely complete: it says what is returned (items and their state) and the inspection use case. It could be richer about pagination or included relationships, but those are covered in the schema.

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 id, limit, include, and next_url are already documented in the input schema. The description only implies that id refers to a review submission; it adds no syntax or format details beyond the schema.

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 states a specific verb and resource: list the items inside a review submission and each item's state. It also distinguishes the result from simply fetching a submission by focusing on what Apple will actually look at.

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?

It gives a clear usage context: check submission contents before handing over to Apple. It does not explicitly name alternatives such as review_submissions__get or state when not to use this tool, so it falls short of full routing guidance.

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