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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

beta_testers_create_instance

Create a beta tester record in App Store Connect by POSTing a JSON:API BetaTesterCreateRequest body, enabling TestFlight tester management.

Instructions

POST /v1/betaTesters (POST /v1/betaTesters) Body shape: see OpenAPI components.schemas.BetaTesterCreateRequest for the full JSON:API envelope.

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": {
      "body": "<body>"
    },
    "name": "beta_testers_create_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesJSON body. Shape: components.schemas.BetaTesterCreateRequest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

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 behavioral burden, yet it discloses nothing about side effects, authentication, idempotency, or what the JSON:API envelope must contain. The only useful trace is a pointer to the OpenAPI component for the body shape, which is invocation-related rather than behavioral.

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

Conciseness3/5

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

It is brief and front-loaded with the route, but the path is duplicated inside parentheses for no reason and the whole entry is under-specifying rather than tightly written. Every clause is terse, but one is pure redundancy.

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 create operation with a nested, undocumented JSON:API body and no annotations or output schema, the description supplies only an endpoint and a documentation pointer. An agent still lacks the behavioral and contextual framing needed to invoke it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is nominally 100%, but the single 'body' property is a free-form object (additionalProperties: {}) with no real structure. The description compensates by naming the exact OpenAPI schema (components.schemas.BetaTesterCreateRequest) the agent must consult, which is genuine added value over the schema itself.

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 only restates the HTTP route (POST /v1/betaTesters) already implied by the tool name, and the parenthetical repeats the identical path verbatim. It never states in words that this creates a beta tester or what one is. This is closer to a tautology of the name than a stated purpose.

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 when-to-use, no prerequisite, and no differentiation from siblings such as beta_testers_get_collection, beta_testers_get_instance, beta_testers_delete_instance, or beta_tester_invitations_create_instance. The agent must infer the appropriate context entirely from the name and route.

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