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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

beta_groups_app_get_to_one_relationship

Fetch the app relationship for a beta group by ID. Identify the app tied to a TestFlight beta group in App Store Connect.

Instructions

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

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_app_get_to_one_relationship"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.8/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 discharges none of it. The only implicit signal is 'GET' (read-only), with no mention of auth requirements, response shape, pagination, or error behavior.

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 the single sentence is pure duplication — the same endpoint string appears twice with no additional information. Brevity here comes from under-specification rather than efficiency.

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?

No output schema exists, so the description should describe the returned relationship resource, yet it says nothing about what the beta group's app relationship contains. For a relationship-fetch endpoint in a large API surface, this 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% and there is only one required parameter ('id', documented as 'the id of the requested resource'), which already conveys the semantics. The description adds nothing, so the baseline of 3 applies for a well-covered single-param schema.

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 verbatim restatement of the tool name and endpoint path ('GET /v1/betaGroups/{id}/relationships/app') duplicated in parentheses. It signals an HTTP GET on a beta-group/app relationship, but adds no plain-language statement of what is actually retrieved or how it differs from sibling tools like beta_groups_app_get_to_one_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 when-to-use guidance, no prerequisites, and no mention of the near-identical sibling beta_groups_app_get_to_one_related or beta_groups_get_instance. The agent is left to infer entirely from the path string.

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