Skip to main content
Glama
Sign In
App Store Connect MCP

App Store Connect MCP

by beautyfree
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get beta group

get-beta-group
Read-onlyIdempotent

Retrieve detailed information about a specific beta group using its App Store Connect ID. Includes metadata and TestFlight settings.

Instructions

Get detailed information about a specific beta group

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": {
      "betaGroupId": "<betaGroupId>"
    },
    "name": "get-beta-group"
  }
}

Input Schema

NameRequiredDescriptionDefault
betaGroupIdYesApp Store Connect beta group ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.6

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering the safety profile. The description adds no additional behavioral context such as return format or authentication requirements, but it does not contradict the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence with no redundant words. It is front-loaded with the verb and resource, making the purpose immediately clear.

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

Completeness4/5

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

For a simple get operation with one parameter and comprehensive annotations, the description is adequate. It clearly states the purpose and implies a detailed response, though it does not enumerate the response fields or error behavior. Given the low complexity, this is sufficient.

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?

The only parameter betaGroupId is fully described in the schema as 'App Store Connect beta group ID', providing complete coverage. The description does not add further semantics, but with 100% schema coverage, a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Get' and resource 'beta group', clearly indicating a retrieval operation. The qualifier 'specific' distinguishes it from the sibling tool list-beta-groups, though it does not explicitly mention that distinction.

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 is provided on when to use this tool versus alternatives like list-beta-groups. There is no mention of prerequisites, exclusions, or scenarios where another tool would be more appropriate.

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