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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

beta_groups_beta_testers_get_to_many_relationship

Retrieve the beta testers associated with a specific beta group ID, with optional pagination, to manage TestFlight tester assignments.

Instructions

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

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_groups_beta_testers_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.9/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 behavioral burden, and it discloses nothing. It does not say that relationship endpoints return resource identifier linkage rather than full tester objects (the key differentiator from the *_related sibling), nor anything about pagination via limit, auth requirements, or response shape.

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?

There is only one short string, but the parenthesis duplicates the path verbatim, adding zero information. It is under-specified rather than concise, and nothing is front-loaded beyond the URL.

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, no output schema, and no prose, an agent has no idea what a successful response contains or how this differs from beta_groups_beta_testers_get_to_many_related. For a relationship endpoint where that distinction is the entire point, the description is 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% — 'id' is documented as 'the id of the requested resource' and 'limit' as 'maximum resources per page'. With the schema doing the heavy lifting, the baseline of 3 applies; the description adds no additional meaning.

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 a raw endpoint path repeated verbatim in parentheses: 'GET /v1/betaGroups/{id}/relationships/betaTesters (. . .)'. It effectively restates the tool name in URL form rather than stating in plain language what the tool returns, and it never distinguishes this relationship endpoint from the sibling beta_groups_beta_testers_get_to_many_related or beta_groups_beta_testers_create/delete_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 Guidelines2/5

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

No guidance on when to call this versus the many sibling relationship tools. The path implies reading the betaTesters linkage of a beta group, but nothing tells the agent when this is the right choice over the *_related variant or the create/delete relationship variants.

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