Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

apps__beta_feedback_crash_submissions__list

Read-onlyIdempotent

Retrieve beta feedback crash submissions for an app, filterable by build, tester, OS, and device details to diagnose issues and improve test coverage.

Instructions

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

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_betaFeedbackCrashSubmissionsNothe fields to include for returned resources of type betaFeedbackCrashSubmissions 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_betaFeedbackCrashSubmissions
      Added value: +{
+  "description": "the fields to include for returned resources of type betaFeedbackCrashSubmissions 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",
+      "crashLog",
+      "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=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the GET endpoint confirmation and the app-scoping constraint, which is useful but minimal; it does not discuss pagination, response size, or filtering behavior. With strong annotations, a 3 is appropriate.

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?

A single front-loaded sentence states verb, resource, and scope, with the endpoint path appended as a compact reference. Every word earns its place and nothing is redundant with the schema or annotations.

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 list operation with 13 parameters, the schema carries the full parameter burden and the annotations carry the full safety burden, so the description only needs to orient the agent on resource and scope, which it does. It could optionally note the relationship to the screenshot-submissions sibling, but nothing essential to invoking the tool correctly is missing.

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%, with all 13 parameters individually documented (including behavioral notes like the empty-list-on-no-match filter behavior and the include relationship cost). The description itself adds no parameter-level meaning beyond echoing the endpoint's {id} placeholder, so the baseline 3 applies.

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), resource (beta feedback crash submissions), and scope (belonging to an app), which unambiguously identifies what the tool does. This clearly distinguishes it from siblings like beta_feedback_crash_submissions__get/delete (single-resource operations) and apps__beta_feedback_screenshot_submissions__list (a different submission type) without needing to open the schema.

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 scope 'belonging to an app' implies the use case: retrieving all crash submissions for one app, keyed by the required id. However, the description offers no explicit when-to-use guidance, exclusions, or named alternatives, even though the near-identical sibling apps__beta_feedback_screenshot_submissions__list exists and could easily be confused with this tool.

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