Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

beta_testers__list

Read-onlyIdempotent

List beta testers from App Store Connect with filters for email, name, app, build, beta group, or invite type. Sort and paginate results to find specific testers for your testing workflow.

Instructions

List beta testers. [GET /v1/betaTesters]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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_idNofilter by id(s)
filter_appsNofilter by id(s) of related 'apps' Takes a 'apps' 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_emailNofilter by attribute 'email'
filter_buildsNofilter by id(s) of related 'builds' Takes a 'builds' 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_lastNameNofilter by attribute 'lastName'
filter_firstNameNofilter by attribute 'firstName'
filter_betaGroupsNofilter by id(s) of related 'betaGroups' Takes a 'betaGroups' 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_inviteTypeNofilter by attribute 'inviteType'
fields_betaTestersNothe fields to include for returned resources of type betaTesters Return only these attributes. A full row set can exceed 200 KB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.2.0
    • changedInput schema / properties / filter_apps / description
      Previous value: -"filter by id(s) of related 'apps'"New value: +"filter by id(s) of related 'apps' Takes a 'apps' 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_betaGroups / description
      Previous value: -"filter by id(s) of related 'betaGroups'"New value: +"filter by id(s) of related 'betaGroups' Takes a 'betaGroups' 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_builds / description
      Previous value: -"filter by id(s) of related 'builds'"New value: +"filter by id(s) of related 'builds' Takes a 'builds' 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."
  2. Changed3 schema fields changedv2.0.0
    • addedInput schema / properties / fields_betaTesters
      Added value: +{
+  "description": "the fields to include for returned resources of type betaTesters Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "firstName",
+      "lastName",
+      "email",
+      "inviteType",
+      "state",
+      "appDevices",
+      "apps",
+      "betaGroups",
+      "builds"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • 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."
  3. First observedv1.3.0

TDQS

A3.7/5.0
Behavior4/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 behavioral safety is clear. The description adds minimal extra behavioral context (just the HTTP method and endpoint), but with strong annotations the bar is lower. No contradictions exist.

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 extremely concise (two brief sentences including the URL). Every word is necessary and no filler exists. It's front-loaded with the core action and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of 13 parameters and no output schema, the description is somewhat lacking. It doesn't explain return values or common usage patterns. However, the strong annotations and fully described schema parameters partially compensate. An agent might need to infer pagination and filtering behavior from parameter names alone, which could be better explained.

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 every parameter has a description. The tool's description does not add any extra meaning beyond the schema; it relies entirely on the structured field descriptions. Baseline is 3 because the schema does the heavy lifting, and the description adds no compensation for the lack of richer param context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'List beta testers' with the resource and action, and the URL path [GET /v1/betaTesters] reinforces it. It sufficiently distinguishes itself from siblings like beta_testers__get or beta_testers__create, though it does not explicitly differentiate from other list tools.

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 itself provides no guidance on when to use this tool vs alternatives or any context about prerequisites. However, the annotations (readOnlyHint, idempotentHint, destructiveHint) imply it is safe for read-only queries, and the parameter schema includes filtering and pagination hints that an experienced agent could infer usage. An explicit usage note is missing.

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