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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

beta_groups_get_instance

Fetches details for a TestFlight beta group by ID, with optional related apps, builds, testers, and recruitment criteria.

Instructions

GET /v1/betaGroups/{id} (GET /v1/betaGroups/{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_groups_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
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
fields_betaGroupsNothe fields to include for returned resources of type betaGroups
limit_betaTestersNomaximum number of related betaTesters returned (when they are included)
fields_betaTestersNothe fields to include for returned resources of type betaTesters
fields_betaRecruitmentCriteriaNothe fields to include for returned resources of type betaRecruitmentCriteria

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only implies a read operation via 'GET' and does not describe authentication requirements, error behavior, response format, or anything about the 9 include/fields/limit parameters that materially affect behavior.

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?

The description is extremely short but wastes most of its space duplicating the same raw endpoint in parentheses. It is under-specified rather than concise, offering no front-loaded explanatory information that would help an agent select or invoke the tool.

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 tool with 9 parameters, sparse relationships, and no output schema or annotations, the description says nothing beyond the HTTP path. It is completely inadequate as a standalone explanation of what this operation returns or how to use its include/fields/limit options.

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 all 9 parameters are documented in the schema, including the required id, include relationships, field selections, and limits. The description adds no parameter meaning beyond what the schema already provides, which is the baseline expectation when coverage is high.

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

Purpose3/5

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

The description names a concrete verb (GET) and resource path (betaGroups/{id}), so an agent can infer it fetches a single beta group. However, it is a raw endpoint string with no explanation of what a beta group is or how it differs from the sibling beta_groups_get_collection, leaving sibling differentiation implicit.

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

Usage Guidelines2/5

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

The description provides no guidance about when to use this tool versus alternatives such as beta_groups_get_collection or beta_groups_beta_testers_get_to_many_relationship. There are no conditions, prerequisites, or exclusions stated; the agent must infer usage from the endpoint path alone.

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