app-publish-mcp

apple_create_beta_group

Creates a TestFlight beta group in App Store Connect, letting you configure testers, public link access, feedback, and build availability for app distribution.

Instructions

Create a beta group

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": {
      "appId": "<appId>",
      "name": "<name>"
    },
    "name": "apple_create_beta_group"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Group name
`appId`	Yes	App ID
`feedbackEnabled`	No	Enable feedback
`isInternalGroup`	No	Internal group for App Store Connect team members
`publicLinkLimit`	No	Max testers via public link
`publicLinkEnabled`	No	Enable public TestFlight link
`hasAccessToAllBuilds`	No	Auto-enable all new builds

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.7.0Oct 25, 2026

changedInput schema / properties / isInternalGroup / description

Previous value: -"Is internal group (Apple employees)"New value: +"Internal group for App Store Connect team members"

First observedv0.3.1Mar 19, 2026

TDQS

C2.4/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, yet it only implies a mutating create. It does not cover permissions, whether the group is immediately usable, defaults for feedbackEnabled/hasAccessToAllBuilds, or what is returned.

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?

A single four-word sentence is technically concise but is under-specification rather than efficient communication; it spends no words on the required appId/name or the five optional configuration flags.

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

Completeness2/5

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

For a 7-parameter mutation with no annotations and no output schema, the description is far too thin. An agent cannot learn from it what a beta group is in TestFlight terms or how the optional flags affect tester behavior.

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% and all 7 parameters are documented in the schema, so the baseline of 3 applies. The description adds no meaning beyond the schema, such as which options are mutually exclusive or typical default choices.

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 states a verb and resource (create a beta group), so the basic action is identifiable. But it is essentially a restatement of the tool name and offers no scope or differentiation from siblings such as apple_list_beta_groups, apple_delete_beta_group, or apple_add_beta_testers_to_group.

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?

There is no guidance on when to create a beta group versus adding testers to an existing one, no prerequisites (an appId is required), and no mention of alternatives among the many sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server