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

App Store Connect MCP Server

by yunyang088
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_app_store_version

Creates a new version for an app on App Store Connect. Requires app ID, platform, and version string; optionally set build and release type.

Instructions

Create a new app store version for an 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>",
      "platform": "<platform>",
      "versionString": "<versionString>"
    },
    "name": "create_app_store_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesThe ID of the app
buildIdNoID of the build to associate with this version (optional)
platformYesThe platform for this version
copyrightNoCopyright text for this version (optional)
releaseTypeNoHow the app should be released
versionStringYesVersion string in format X.Y or X.Y.Z (e.g., '1.0' or '1.0.0')
earliestReleaseDateNoEarliest release date in ISO 8601 format (required when releaseType is SCHEDULED)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.3

TDQS

B3.2/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 full burden. It only states the tool creates a version but does not disclose side effects, required permissions, or behavior when parameters are omitted (e.g., buildId).

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 a single concise sentence front-loading the purpose. No wasted words.

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?

The tool has 7 parameters, multiple enums, and no output schema. The description provides no context about the result, constraints, or workflow integration, making it insufficient for full understanding.

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 coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema; it does not explain or elaborate on any parameters.

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 clearly states the action ('Create') and the resource ('a new app store version for an app'). It differentiates from sibling tools like list_app_store_versions and update_app_store_version_localization by specifying creation.

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 or alternatives. There is no mention of prerequisites, when not to use, or how it differs from other tools like update_app_store_version_localization.

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