Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

beta_feedback_crash_submissions__get

Read-onlyIdempotent

Fetch a single beta feedback crash submission by ID with optional build and tester relationships. Retrieve only the specified fields, reducing extra API calls when reviewing crash reports.

Instructions

Read one beta feedback crash submission by ID. [GET /v1/betaFeedbackCrashSubmissions/{id}]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID from the matching list call.
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.
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.0.1
    • addedInput schema / properties / id / description
      Added value: +"ID from the matching list call."
  2. Changed3 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."
  3. 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 and destructiveHint=false, so the safety profile is covered. The description adds no extra behavioral context such as error cases, authentication, or rate limits. It doesn't contradict the annotations, but it doesn't enrich them either.

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 sentence plus the HTTP endpoint. It is extremely concise, front-loaded with the action, and contains no filler. Every word earns its place.

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?

Given the tool is a simple read-by-ID operation with well-documented parameters, the description is mostly complete. However, it does not explain the response structure or default fields, but the schema covers the include/fields modifiers. A small gap, but adequate for a straightforward GET.

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% coverage with descriptions for all three parameters (id, include, fields_betaFeedbackCrashSubmissions). The description itself adds no parameter-specific detail beyond what the schema already provides, so the baseline of 3 is appropriate.

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 uses the specific verb 'Read' and clearly identifies the resource 'one beta feedback crash submission by ID'. This distinguishes it from list operations and other get tools, making the purpose unambiguous.

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 description implies usage when you have an ID (from a list call) but does not explicitly state when to use this tool versus alternatives like the list or delete sibling tools. There are no exclusions or alternative suggestions, so it's basic but not misleading.

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