Skip to main content
Glama
Sign In
App Store Connect MCP Server

App Store Connect MCP Server

by yunyang088
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_app_store_versions

Retrieve all App Store versions for a specific app, with optional filters for platform, release state, and version string.

Instructions

Get all app store versions for a specific app

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": "list_app_store_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesThe ID of the app
limitNoMaximum number of versions to return (default: 100)
filterNoOptional filters for app store versions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.3

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided. Description only states it retrieves versions, but does not disclose pagination behavior, rate limits, ordering, or whether results are complete. The limit parameter implies pagination but is not explained.

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

Conciseness4/5

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

Description is a single concise sentence that clearly states the tool's function. No unnecessary words, but could benefit from slight expansion on usage context.

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?

No output schema; description does not explain return values or format. Does not mention default limit, sorting, or handling of pagination. Given three parameters and a nested filter object, more detail is needed.

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?

Input schema has 100% description coverage for all parameters. The description adds no additional meaning beyond what's in the schema. Baseline of 3 is appropriate.

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?

Description uses specific verb 'Get' and resource 'app store versions' with a clear scope 'for a specific app'. It distinguishes from sibling tools like create_app_store_version (create) and list_app_store_version_localizations (different resource).

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?

No guidance on when to use this tool versus alternatives (e.g., list_apps, create_app_store_version). No mention of prerequisites or when not to use it.

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