Skip to main content
Glama
Sign In
app-store-connect-mcp

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

beta_testers_get_instance

Retrieve a specific beta tester's App Store Connect details by ID, with options to include related apps, beta groups, and builds for TestFlight management.

Instructions

GET /v1/betaTesters/{id} (GET /v1/betaTesters/{id})

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "beta_testers_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
limit_appsNomaximum number of related apps returned (when they are included)
fields_appsNothe fields to include for returned resources of type apps
limit_buildsNomaximum number of related builds returned (when they are included)
fields_buildsNothe fields to include for returned resources of type builds
limit_betaGroupsNomaximum number of related betaGroups returned (when they are included)
fields_betaGroupsNothe fields to include for returned resources of type betaGroups
fields_betaTestersNothe fields to include for returned resources of type betaTesters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.7/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full disclosure burden, and it discloses nothing: no authentication requirements, no rate-limit behavior, no pagination semantics for the relationship includes, and no indication of what is returned or whether the operation is safe/read-only.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but brevity here is under-specification rather than conciseness; the route is also needlessly repeated verbatim inside parentheses, so even the one line contains no earning content.

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

Completeness1/5

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

For a 9-parameter read tool with no annotations and no output schema, the description should at minimum characterize the resource and the include/fields behavior. A bare route string leaves the agent with essentially no usable context.

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% (9 of 9 params documented, including include, limits, and field selectors), so the schema does the heavy lifting. The description adds nothing beyond the route, leaving baseline 3 appropriate under the high-coverage rule.

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

Purpose2/5

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

The description is merely the HTTP route 'GET /v1/betaTesters/{id}' duplicated in parentheses. It restates the tool name (beta_testers_get_instance) rather than explaining in plain language what the tool does or how it differs from sibling tools such as beta_testers_get_collection.

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

Usage Guidelines1/5

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

There is no usage guidance at all: no statement of when to fetch a single beta tester versus the collection, no prerequisites, and no mention of alternatives. An agent must infer everything from the route string.

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