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

App Store Connect MCP Server

by SardorbekR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_app_version

Create a new App Store version for an iOS, macOS, tvOS, or visionOS app. Specify the version number, platform, and release preferences.

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_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesThe App Store Connect app ID
platformYesPlatform for the version
versionStringYesVersion number (e.g., '1.0.0', '2.1')
releaseTypeNoRelease type
copyrightNoCopyright text for the version
earliestReleaseDateNoEarliest release date (ISO 8601 format) for SCHEDULED release type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/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 'create' without disclosing side effects, error conditions, or expected outcomes (e.g., does it check for duplicates? what are required permissions?). Minimal behavioral context beyond the action verb.

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?

Single sentence, front-loaded with verb and object. 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?

Despite having 6 parameters (3 required) and no output schema, the description is extremely brief. Missing context about return value, error handling, constraints, or side effects. For a creation tool, more completeness is expected.

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 the schema already documents all parameters. The description adds no parameter-specific information beyond what is in the schema, so baseline score 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 clearly states it creates an App Store version, with verb and resource. Distinct from sibling tools like create_version_localization or get_app_version.

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?

No explicit when-to-use or alternatives guidance. While the purpose is clear, there is no mention of prerequisites or when to choose this over related 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