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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_center_challenge_versions_create_instance

Create an instance of a Game Center challenge version via App Store Connect. Use it to define challenge version details for Game Center challenges.

Instructions

POST /v1/gameCenterChallengeVersions (POST /v1/gameCenterChallengeVersions) Body shape: see OpenAPI components.schemas.GameCenterChallengeVersionCreateRequest 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": {
      "body": "<body>"
    },
    "name": "game_center_challenge_versions_create_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesJSON body. Shape: components.schemas.GameCenterChallengeVersionCreateRequest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2/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, and it discloses nothing about side effects, required auth/roles, or what state the create operation affects. The only behavioral hint is 'POST', which is already implied by the tool name. There is no mention of idempotency, rate limits, or required parent relationships.

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?

The description is short but wastes space by repeating the identical path twice inside parentheses. It is not front-loaded with any actionable content, and the one informative sentence (schema reference) is buried behind the redundant path.

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?

This is a mutation tool with a nested, opaque request body, no annotations, and no output schema. The description defers all detail to an external OpenAPI document and provides no in-band information about required nested fields, auth, or result, which is insufficient for correct invocation.

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?

There is a single required 'body' parameter whose schema description coverage is 100%, and the schema already points to components.schemas.GameCenterChallengeVersionCreateRequest. The description merely repeats that pointer without adding field-level meaning, so the baseline 3 for fully-covered parameters is appropriate.

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 restates the HTTP method and URL path already encoded in the tool name, so it is largely tautological. It does not explain what a game center challenge version is or how creating one differs from e.g. game_center_challenges_create_instance or the version_releases sibling. The only added value is pointing at the request body schema.

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 statement of when to call this tool versus the many sibling create/relationship tools, no prerequisites, and no exclusions. The create semantics are only implied by the name and the POST verb. An agent must infer usage entirely.

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