Set up a beta group to distribute builds to testers—internal for your team or external for Apple's review.
Make a TestFlight group to organise testers — an internal one for the team, or an external one Apple reviews before it can receive builds. [POST /v1/betaGroups]
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | JSON:API request body (Apple schema: BetaGroupCreateRequest). |
Changes observed during successful MCP inspections.
v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the agent knows this is a non-idempotent write. The description adds the key behavioral context about external groups requiring Apple review before receiving builds, which is valuable. It does not disclose details like required app relationship or that builds can be linked at creation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that front-loads the purpose, names the key distinction (internal vs external), and includes the endpoint reference. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the tool's core purpose and key behavioral distinction, while the schema fully documents required fields (name, app relationship) and optional attributes (feedbackEnabled, publicLink, etc.). The missing output schema is acceptable for a create operation whose response mirrors the request in Apple's API. Could slightly benefit from mentioning that an app relationship is mandatory, but the schema carries that.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 1 parameter with 100% description coverage (the body is explained as the JSON:API request body). The description adds meaning by framing the purpose (organizing testers, internal vs external), which helps the agent understand the relationship and attributes. The schema itself is deeply nested but well-typed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states a clear verb ('Make a TestFlight group') with a specific resource, and distinguishes the two main use cases (internal team vs external Apple-reviewed) directly in the text. It also maps to the endpoint [POST /v1/betaGroups], making it unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly conveys when to use this tool: creating a TestFlight group, and distinguishes internal vs external groups with different review implications. It doesn't explicitly name alternative tools, but the sibling list shows related beta_group operations with different verbs (list/get/update/delete), making the use case clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.