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_delete_to_many_relationship

Remove beta groups from a beta tester in App Store Connect by deleting the specified relationship records for a given tester ID.

Instructions

DELETE /v1/betaTesters/{id}/relationships/betaGroups (DELETE /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_delete_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/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. The 'DELETE' verb implies a destructive mutation, but it never states that this only severs the relationship (not deletes the tester or group), whether it is idempotent, or what permissions are required. The pointer to the OpenAPI request schema is the only behavioral context offered.

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 short, but the parenthetical repeat of the exact same endpoint '(DELETE /v1/betaTesters/{id}/relationships/betaGroups)' is pure redundancy, and the body-shape sentence is awkwardly phrased. Removing the duplication would leave a tighter, front-loaded definition.

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 two-parameter relationship-delete with no annotations and no output schema, the definition is thin: it does not explain what the JSON:API linkages body should contain, what the effect on existing relationships is, or what a caller should expect. Only an external OpenAPI reference is given, which the agent cannot necessarily resolve.

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%, so the two parameters (id, body) are already documented in the schema. The description names the body schema (BetaTesterBetaGroupsLinkagesRequest) but adds no meaning beyond what the schema field already says, so the baseline of 3 applies.

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 embeds the operation in the raw URL (DELETE /v1/betaTesters/{id}/relationships/betaGroups), which does convey verb and resource, but there is no plain-language statement like 'removes beta groups from a beta tester.' It does not distinguish itself from the sibling create/get/related variants of the same relationship beyond the 'DELETE' token.

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 guidance, no prerequisites, and no mention of alternatives such as beta_testers_beta_groups_get_to_many_relationship or beta_groups_beta_testers_delete_to_many_relationship. The agent must infer all routing from the URL path alone.

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