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

appstore-connect-mcp

by tomoki013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

[Write] Update an App Store version

asc_version_update

Update an existing App Store version's version string, copyright, release type, or earliest release date. Preview changes with a dry run before applying.

Instructions

Write. Partially updates an existing App Store version: versionString, copyright, releaseType (MANUAL/AFTER_APPROVAL/SCHEDULED), earliestReleaseDate. Supports dryRun to preview the change as an old → new diff without applying it.

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>",
      "version": "<version>"
    },
    "name": "asc_version_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesBundle id, app name, or App Store Connect app id
dryRunNoPreview only, do not apply
versionYesCurrent version string identifying the version, e.g. "1.1"
copyrightNo
releaseTypeNo
versionStringNoNew version string
earliestReleaseDateNoISO 8601 date-time, only meaningful with releaseType SCHEDULED

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It adds valuable context: partial update semantics, dryRun preview as old→new diff without applying, and lists updatable fields. However, it does not mention permissions, response format, idempotency, or reversibility, which is a gap for a mutation tool.

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?

Two sentences, front-loaded with the operation and field list. Every sentence earns its place, with no redundant phrasing or filler.

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

Completeness3/5

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

Given no annotations, no output schema, and 7 parameters, the description covers the core action and dryRun behavior but omits return value details, prerequisites (e.g., version must exist), and edge-case constraints. It is adequate but lacks a fuller picture.

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

Parameters4/5

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

Schema coverage is 71% (5 of 7 properties documented). The description adds meaning by inlining releaseType enum values (MANUAL/AFTER_APPROVAL/SCHEDULED) and clarifying dryRun behavior. It also helps compensate for missing schema descriptions on copyright and releaseType by naming them as updatable fields.

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 'Partially updates an existing App Store version' with specific verb and resource, and enumerates updatable fields (versionString, copyright, releaseType, earliestReleaseDate). This distinguishes it from sibling tools like asc_version_create (create) and asc_version_get (get).

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

Usage Guidelines4/5

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

Provides clear context: use for partial updates to existing versions, with dryRun option. Does not explicitly exclude alternatives or name sibling tools, but the 'existing' and 'partially updates' framing implies it is not for creation or full replacement.

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