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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_center_leaderboard_images_v2_update_instance

Update a Game Center leaderboard image v2 instance by ID, sending a JSON:API PATCH body to change its attributes in App Store Connect.

Instructions

PATCH /v2/gameCenterLeaderboardImages/{id} (PATCH /v2/gameCenterLeaderboardImages/{id}) Body shape: see OpenAPI components.schemas.GameCenterLeaderboardImageV2UpdateRequest 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_leaderboard_images_v2_update_instance"
  }
}

Input Schema

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

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 only conveys that this is a PATCH (implying partial update) and points to an OpenAPI schema for the body envelope; it says nothing about permissions, reversibility, what fields get modified, or the JSON:API mutation semantics.

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?

It is a single short sentence, but it wastes space by duplicating the PATCH path verbatim in parentheses and leans on an external schema reference rather than stating anything actionable.

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 a nested body object, no annotations, and no output schema, the description is incomplete: it omits return behavior, partial-update semantics, required permissions, and any indication of what the body should contain beyond a schema name.

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 schema already documents both the id and body parameters. The description adds a reference to the GameCenterLeaderboardImageV2UpdateRequest component for the body envelope shape, which is marginally helpful but largely redundant with the schema's own body description.

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 the HTTP verb and resource path (PATCH /v2/gameCenterLeaderboardImages/{id}), which conveys that this updates a Game Center leaderboard image v2 resource. However, it is essentially a restatement of the name/endpoint with no differentiation from the many sibling update tools (e.g. game_center_leaderboard_set_images_v2_update_instance, game_center_leaderboard_images_update_instance).

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 guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The agent is left to infer usage purely from the endpoint path.

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