Skip to main content
Glama
Sign In
appstore-connect-mcp

appstore-connect-mcp

by tomoki013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

[Read] List App Store versions

asc_versions_list

List all App Store versions for an app, showing version string, platform, review state, and release details. Use this to track version history and submission status.

Instructions

Read-only. Lists all App Store versions for an app (version string, platform, App Store review state, created date, copyright, releaseType, earliestReleaseDate).

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": {
      "appId": "<appId>"
    },
    "name": "asc_versions_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesBundle id, app name, or App Store Connect app id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Since no annotations are provided, the description carries the disclosure burden. It explicitly states 'Read-only' and enumerates the output fields, providing transparency about the operation's non-mutating nature and return structure. However, it does not mention potential pagination or permissions, but for a simple list tool this is adequate.

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

Conciseness5/5

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

The description is two concise sentences (~20 words) that front-load the behavior ('Read-only. Lists all App Store versions') and then list the returned fields. No filler or redundancy.

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

Completeness5/5

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

For a read-only list tool with a single parameter and no output schema, the description adequately covers purpose, output fields, and safety. It specifies 'all' versions, giving a complete scope. No annotations or output schema exist, but the description compensates sufficiently.

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?

The input schema coverage is 100% with appId fully described ('Bundle id, app name, or App Store Connect app id'), so the description need not repeat it. The tool description adds no parameter details beyond the schema, consistent with the baseline of 3 for high coverage.

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

Purpose5/5

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

The description uses a specific verb ('lists') and resource ('all App Store versions for an app') alongside explicit output fields (version string, platform, review state, etc.). This clearly distinguishes it from sibling tools like asc_version_get (single version) and asc_version_create, despite not naming them.

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 description implies usage for retrieving a collection of versions but does not provide explicit guidance on when to choose this tool over siblings like asc_version_get or mention any exclusions. The 'Read-only' prefix and list semantics suggest contexts, but no when-not-to-use or alternative tools are stated.

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