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_get_to_many_relationship

Retrieve beta groups assigned to a specific beta tester in App Store Connect to manage TestFlight distribution and tester access.

Instructions

GET /v1/betaTesters/{id}/relationships/betaGroups (GET /v1/betaTesters/{id}/relationships/betaGroups)

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>"
    },
    "name": "beta_testers_beta_groups_get_to_many_relationship"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
limitNomaximum resources per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.7/5.0
Behavior1/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 of behavioral disclosure, and it discloses nothing: no auth/permission requirements, no pagination semantics for the 'limit' parameter, no indication of whether the relationship linkage data differs from the 'related' variant. The duplicated path adds no behavioral context.

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?

It is short, but this is under-specification rather than conciseness, and the parenthetical repeats the identical string verbatim, which is pure waste with zero added information.

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

Completeness1/5

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

With no annotations and no output schema, the description must explain the operation, its relationship semantics, and pagination behavior; it explains none of them. For a relationship-fetch endpoint in a large family of near-identical siblings, this is completely inadequate.

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%, with both 'id' and 'limit' documented in the schema, so the baseline of 3 applies. The description adds no meaning beyond the schema — it never mentions the id scoping or page size at all.

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 just the raw HTTP path repeated twice in parentheses: 'GET /v1/betaTesters/{id}/relationships/betaGroups'. It restates the tool name in URL form rather than explaining in plain language what is returned, and it does nothing to distinguish this 'relationship' variant from the sibling 'beta_testers_beta_groups_get_to_many_related'.

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?

No guidance whatsoever on when to use this tool, when not to, or which sibling (e.g. the *_get_to_many_related variant, or beta_groups_beta_testers_get_to_many_relationship) is the right alternative. The agent is left to infer everything from the endpoint path.

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