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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_center_challenge_images_create_instance

Create a Game Center challenge image in App Store Connect by posting a JSON:API request to /v1/gameCenterChallengeImages.

Instructions

POST /v1/gameCenterChallengeImages (POST /v1/gameCenterChallengeImages) Body shape: see OpenAPI components.schemas.GameCenterChallengeImageCreateRequest 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_images_create_instance"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.6/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 behavioral burden for a mutating create operation, and it discloses nothing: no auth/permission requirements, no side effects, no idempotency, no note on what the JSON:API envelope must contain. The only signal ('POST') is already implied by the tool name.

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 it wastes its opening on the endpoint and then repeats the identical path in a redundant parenthetical. Purpose is never front-loaded, and the sentence is machine-generated boilerplate rather than an agent-facing instruction.

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 an unannotated mutation with an opaque body schema and no output schema, the description should at minimum confirm the resource being created and note envelope expectations. Instead it defers entirely to an external OpenAPI component name the agent cannot resolve, leaving the call under-specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, but the single 'body' parameter is an opaque passthrough object (additionalProperties: {}), and the description merely repeats the schema's own pointer to 'components.schemas.GameCenterChallengeImageCreateRequest' verbatim. It adds no meaning beyond the structured field — no required members, no example envelope, no note that it must be JSON:API formatted.

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 text is an HTTP method plus endpoint path ('POST /v1/gameCenterChallengeImages') rather than a statement of purpose. It never says it creates a Game Center challenge image resource, so the agent must infer the verb and resource from the tool name alone. Not misleading, but effectively a tautological restatement of the name.

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

Usage Guidelines1/5

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

There is no when-to-use guidance whatsoever — no mention of prerequisites, no reference to the get/update/delete siblings for the same resource, and no indication of when a challenge image should be created versus another asset type. The agent gets no routing help from a list of hundreds of sibling tools.

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