app-publish-mcp

apple_invite_beta_tester

Invite beta testers by email to selected beta groups, facilitating test flight testing for your app on App Store Connect.

Instructions

Invite a beta tester

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": {
      "email": "<email>",
      "betaGroupIds": "<betaGroupIds>"
    },
    "name": "apple_invite_beta_tester"
  }
}

Input Schema

Name	Required	Description
`email`	Yes	Tester email
`lastName`	No	Last name
`firstName`	No	First name
`betaGroupIds`	Yes	Array of beta group IDs

Schema Changelog

Changes observed during successful MCP inspections.

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 provided; description only says 'Invite' without explaining mutation, state changes, or side effects. Does not disclose if email is sent, if tester record is created, or any permissions needed.

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?

Extremely short (4 words) but under-specified for a tool with 4 parameters and complex sibling relationships. Lacks essential details, making it insufficient for effective use.

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?

Given 4 parameters, no output schema, and sibling tools like 'add_beta_testers_to_group', the description fails to clarify the invitation workflow, the role of betaGroupIds, or expected outcomes.

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 coverage is 100%, so baseline is 3. Description adds no additional meaning beyond the schema; it doesn't reference parameters or explain their role in the invite process.

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?

Description states 'Invite a beta tester' – clear verb+resource but insufficient to distinguish from sibling 'apple_add_beta_testers_to_group' which may also involve inviting. Lacks specificity.

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?

No guidance on when to use this tool vs alternatives like 'apple_add_beta_testers_to_group' or 'apple_remove_beta_testers_from_group'. No prerequisites or context provided.

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

Deploy Server