Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

apps__beta_groups__list

Read-onlyIdempotent

Retrieve beta groups for an app by providing its app ID, bundle ID, or name. Get group attributes such as name, internal group status, and public link configuration.

Instructions

List the beta groups belonging to an app. [GET /v1/apps/{id}/betaGroups]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesApp name, bundle ID (com.example.app) or numeric Apple ID.
limitNomaximum resources per page
next_urlNoAbsolute links.next URL from a previous response.
fields_betaGroupsNothe fields to include for returned resources of type betaGroups 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. 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
    • addedInput schema / properties / fields_betaGroups
      Added value: +{
+  "description": "the fields to include for returned resources of type betaGroups Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "name",
+      "createdDate",
+      "isInternalGroup",
+      "hasAccessToAllBuilds",
+      "publicLinkEnabled",
+      "publicLinkId",
+      "publicLinkLimitEnabled",
+      "publicLinkLimit",
+      "publicLink",
+      "feedbackEnabled",
+      "iosBuildsAvailableForAppleSiliconMac",
+      "iosBuildsAvailableForAppleVision",
+      "app",
+      "builds",
+      "betaTesters",
+      "betaRecruitmentCriteria",
+      "betaRecruitmentCriterionCompatibleBuildCheck"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / id / description
      Removed value: -"Resource identifier."
    • 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

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, fully covering the safety profile. The description adds the GET endpoint, which confirms the read-only nature, but discloses no additional behavioral traits such as pagination behavior, default page size, or response structure. With annotations carrying the safety burden, this is adequate but not additive.

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 sentence plus endpoint reference with zero wasted words. The verb and resource are front-loaded, and the endpoint provides precise API grounding. Every element 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?

For a read-only list operation, the combination of description, schema (100% parameter coverage), and annotations (safe, idempotent) covers the essentials: purpose, required id param, pagination controls, and field selection. The description does not explicitly address pagination sequencing, but the schema's limit and next_url parameters imply it, making the package sufficient for an agent to call this correctly.

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 each of the four parameters (id, limit, next_url, fields_betaGroups) already well-documented in the schema, including the id format options and the 200 KB row-set warning. The tool description itself adds no parameter-level meaning beyond the {id} placeholder in the endpoint, 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 and resource: 'List the beta groups belonging to an app,' with clear scope (app-scoped rather than global). The endpoint [GET /v1/apps/{id}/betaGroups] reinforces the resource and differentiates it from siblings like beta_groups__list and beta_groups__get, which operate at different scopes.

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 phrase 'belonging to an app' implies the use case — you need beta groups for one specific app identified by the id parameter. However, it never explicitly names alternatives or states when NOT to use it versus beta_groups__list (global listing) or beta_groups__get (single record). The usage context is clear but the exclusion logic is left 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