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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_center_achievements_create_instance

Create a Game Center achievement record in App Store Connect by sending the required JSON:API body to the deprecated achievements endpoint.

Instructions

[DEPRECATED] POST /v1/gameCenterAchievements (POST /v1/gameCenterAchievements) Body shape: see OpenAPI components.schemas.GameCenterAchievementCreateRequest 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_achievements_create_instance"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.5/5.0
Behavior2/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. It does disclose the deprecation status, which is genuinely useful, but says nothing about permissions, side effects, or whether the endpoint is still callable — significant gaps for a mutation tool.

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

Conciseness3/5

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

The deprecation warning is correctly front-loaded, but the endpoint is needlessly duplicated ('POST /v1/gameCenterAchievements (POST /v1/gameCenterAchievements)'). It is short overall, yet the redundancy wastes the little space it has.

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?

For a mutation tool with no annotations and no output schema, the description provides only the deprecation flag and an OpenAPI pointer. It omits any guidance on replacements, permissions, or request expectations, leaving the agent under-informed for actually invoking it.

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 the single body parameter is documented as 'components.schemas.GameCenterAchievementCreateRequest'. The description merely echoes that pointer, adding no syntax or field-level meaning beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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

Purpose3/5

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

The description states a concrete HTTP operation and resource (POST /v1/gameCenterAchievements), which implies creating a Game Center achievement, and it flags [DEPRECATED]. However, it never explains in plain terms what the tool creates or how it differs from siblings like game_center_achievements_v2_create_instance, so the agent must infer purpose from the endpoint string.

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?

The [DEPRECATED] tag hints the tool should be avoided, but the description never says when to use this versus the many sibling create tools (notably game_center_achievements_v2_create_instance). An agent is left to guess whether a supported replacement exists.

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