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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

beta_testers_beta_groups_create_to_many_relationship

Links a beta tester to one or more TestFlight beta groups by creating the relationship in App Store Connect, so testers receive the correct builds.

Instructions

POST /v1/betaTesters/{id}/relationships/betaGroups (POST /v1/betaTesters/{id}/relationships/betaGroups) Body shape: see OpenAPI components.schemas.BetaTesterBetaGroupsLinkagesRequest 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": {
      "id": "<id>",
      "body": "<body>"
    },
    "name": "beta_testers_beta_groups_create_to_many_relationship"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
bodyYesJSON body. Shape: components.schemas.BetaTesterBetaGroupsLinkagesRequest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2/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. It does imply a write via the POST verb and points at a body schema, but it says nothing about required permissions, whether the linkage is additive vs replacing, error behavior, or rate limits — significant gaps for a mutation tool with zero annotation coverage.

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 single sentence duplicates the endpoint path twice with no added meaning, so a meaningful fraction of the text is pure redundancy. It is short, but not because it is efficient — it is short because it says almost nothing.

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 mutation tool with no annotations and no output schema, the description should explain the JSON:API linkage envelope, cardinality, and side effects. Instead it defers entirely to an external OpenAPI schema reference an agent may not be able to resolve, leaving the definition inadequate for correct invocation.

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% for both parameters, so the schema already documents 'id' and the JSON body shape. The description merely repeats the schema's own pointer to components.schemas.BetaTesterBetaGroupsLinkagesRequest without adding format, cardinality, or envelope detail beyond what the structured fields supply.

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 is essentially a restatement of the tool name as an HTTP path, duplicated verbatim in parentheses ('POST /v1/betaTesters/{id}/relationships/betaGroups'). It never states in plain language that this adds beta groups to a beta tester, and it does not distinguish itself from siblings like beta_testers_beta_groups_delete_to_many_relationship or beta_testers_beta_groups_get_to_many_relationship.

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

Usage Guidelines1/5

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

There is no when-to-use guidance whatsoever, no mention of the delete/get sibling variants, and no prerequisites or conditions. An agent cannot tell from this text when this tool is the right choice over the closely-named alternatives.

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