Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

apps__beta_feedback_screenshot_submissions__list

Read-onlyIdempotent

List beta feedback screenshot submissions for an app, with filters for build, tester, OS version, device model, and platform. Paginate results and include related records as needed.

Instructions

List the beta feedback screenshot submissions belonging to an app. [GET /v1/apps/{id}/betaFeedbackScreenshotSubmissions]

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_buildNofilter by id(s) of related 'build' Takes a 'build' resource id, read from the call that lists them — not a name. A value that matches nothing returns 200 with an empty list rather than an error.
filter_testerNofilter by id(s) of related 'tester' Takes a 'tester' resource id, read from the call that lists them — not a name. A value that matches nothing returns 200 with an empty list rather than an error.
filter_osVersionNofilter by attribute 'osVersion'
filter_appPlatformNofilter by attribute 'appPlatform'
filter_deviceModelNofilter by attribute 'deviceModel'
filter_devicePlatformNofilter by attribute 'devicePlatform'
filter_build.preReleaseVersionNofilter by id(s) of related 'build.preReleaseVersion' Takes a 'build.preReleaseVersion' resource id, read from the call that lists them — not a name. A value that matches nothing returns 200 with an empty list rather than an error.
fields_betaFeedbackScreenshotSubmissionsNothe fields to include for returned resources of type betaFeedbackScreenshotSubmissions 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. Changed3 schema fields changedv2.2.0
    • changedInput schema / properties / filter_build / description
      Previous value: -"filter by id(s) of related 'build'"New value: +"filter by id(s) of related 'build' Takes a 'build' resource id, read from the call that lists them — not a name. A value that matches nothing returns 200 with an empty list rather than an error."
    • changedInput schema / properties / filter_build.preReleaseVersion / description
      Previous value: -"filter by id(s) of related 'build.preReleaseVersion'"New value: +"filter by id(s) of related 'build.preReleaseVersion' Takes a 'build.preReleaseVersion' resource id, read from the call that lists them — not a name. A value that matches nothing returns 200 with an empty list rather than an error."
    • changedInput schema / properties / filter_tester / description
      Previous value: -"filter by id(s) of related 'tester'"New value: +"filter by id(s) of related 'tester' Takes a 'tester' resource id, read from the call that lists them — not a name. A value that matches nothing returns 200 with an empty list rather than an error."
  3. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / id / description
      Added value: +"ID from the matching list call."
  4. Changed4 schema fields changedv2.0.0
    • addedInput schema / properties / fields_betaFeedbackScreenshotSubmissions
      Added value: +{
+  "description": "the fields to include for returned resources of type betaFeedbackScreenshotSubmissions Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "createdDate",
+      "comment",
+      "email",
+      "deviceModel",
+      "osVersion",
+      "locale",
+      "timeZone",
+      "architecture",
+      "connectionType",
+      "pairedAppleWatch",
+      "appUptimeInMilliseconds",
+      "diskBytesAvailable",
+      "diskBytesTotal",
+      "batteryPercentage",
+      "screenWidthInPoints",
+      "screenHeightInPoints",
+      "appPlatform",
+      "devicePlatform",
+      "deviceFamily",
+      "buildBundleId",
+      "screenshots",
+      "build",
+      "tester"
+    ],
+    "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."
    • 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."
  5. First observedv1.3.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the read-only nature is covered. The description adds the app-scoping and endpoint context but does not disclose additional behavioral details such as pagination behavior or response characteristics, which is acceptable but not additive beyond 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 that names the operation and resource, followed by a compact endpoint reference. There is no wasted wording, and the information is immediately useful.

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?

Although the tool has 13 parameters and no output schema, the schema descriptions are thorough and the list semantics make the return shape inferable. The description provides the key operation and scope; only a brief note about pagination or expected response would make it fully complete.

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?

The input schema has 100% description coverage, including rich details on the app id, filters, sort, and field selection. The description adds only the implied path parameter {id} from the endpoint, so it does not meaningfully improve on the schema's parameter documentation.

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 ('List') and a specific resource ('beta feedback screenshot submissions') scoped to an app, and includes the exact GET endpoint. This clearly distinguishes it from siblings like the singular getter and deleter for the same resource.

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

Usage Guidelines3/5

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

The intended use is clear from the wording: use this to list the screenshot submissions for an app. However, it gives no explicit guidance on when to prefer this over alternatives such as beta_feedback_screenshot_submissions__get or apps__beta_feedback_crash_submissions__list, leaving that to inference.

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