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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_center_activities_achievements_create_to_many_relationship

Links one or more achievements to a Game Center activity by creating the to-many relationship via App Store Connect. Deprecated endpoint.

Instructions

[DEPRECATED] POST /v1/gameCenterActivities/{id}/relationships/achievements (POST /v1/gameCenterActivities/{id}/relationships/achievements) Body shape: see OpenAPI components.schemas.GameCenterActivityAchievementsLinkagesRequest 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": {
      "id": "<id>",
      "body": "<body>"
    },
    "name": "game_center_activities_achievements_create_to_many_relationship"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
bodyYesJSON body. Shape: components.schemas.GameCenterActivityAchievementsLinkagesRequest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.3/5.0
Behavior3/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. It usefully discloses that the tool is deprecated and that it is a write operation (POST) requiring a JSON:API envelope, but it says nothing about permissions, whether existing linkages are appended or replaced, idempotency, 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.

Conciseness3/5

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

The description is short and front-loads the critical [DEPRECATED] flag. However, the endpoint URL is repeated verbatim in parentheses, which is pure redundancy that adds no information.

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

Completeness3/5

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

For a deprecated, annotation-free mutation with no output schema, the description covers the endpoint, the deprecation status, and where to find the body schema. It omits what the linkage creation actually does to existing relationships and any response expectation, leaving gaps for a tool of this complexity.

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%, so the baseline is 3. The body-shape pointer to components.schemas.GameCenterActivityAchievementsLinkagesRequest largely duplicates the schema's own body description and does not explain the linkage payload semantics beyond what the schema already states.

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 names a concrete verb (POST) and a fully-qualified resource path (/v1/gameCenterActivities/{id}/relationships/achievements), which distinguishes it from the sibling DELETE and _v2_ variants of the same relationship. It is specific enough for an agent to identify the operation, though it never states the effect in plain language (link achievements to an activity).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The [DEPRECATED] marker is a meaningful when-not-to-use signal, so this is more than no guidance at all. However, it never names a replacement (e.g. the _v2_ or delete sibling) or explains the conditions under which this relationship endpoint should be used, leaving the agent to infer the alternative.

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