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

appstore-connect-mcp

by tomoki013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

[Write] Update App Store version metadata

asc_metadata_update

Update localized App Store metadata fields (description, keywords, promotional text, etc.) for a specific version and locale. Use dry-run to preview the diff before applying changes.

Instructions

Write. Partially updates localized App Store metadata for a version/locale (description, keywords, promotionalText, whatsNew, supportUrl, marketingUrl). Locale is required and must be explicit (e.g. en-US, ja). 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>",
      "locale": "<locale>"
    },
    "name": "asc_metadata_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesBundle id, app name, or App Store Connect app id
dryRunNoPreview only, do not apply
localeYesLocale to update, e.g. "en-US"
versionYesApp Store version string, e.g. "1.1"
keywordsNo
whatsNewNo
supportUrlNo
descriptionNo
marketingUrlNo
promotionalTextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that this is a partial update and mentions the dryRun preview behavior, which is valuable. Yet it does not explain what happens to unspecified fields (merge semantics), nor does it state permissions or error cases, leaving some behavioral gaps.

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 'Write' and 'Partially updates', and every word adds value. There is no redundancy or filler, making it easy to parse quickly.

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

Completeness4/5

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

Given the tool's complexity (10 params, no output schema, no annotations), the description covers the core operation, the target fields, the locale requirement, and dryRun. It lacks details on response format or creation semantics, but for a partial update tool the essentials are present.

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 only 40%, but the description compensates by enumerating all updatable fields (description, keywords, promotionalText, whatsNew, supportUrl, marketingUrl). It also clarifies the dryRun parameter's role (preview as old→new diff) and the locale requirement (must be explicit), adding meaning beyond the schema.

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 ('updates') and a precise resource ('localized App Store metadata for a version/locale'), listing the exact fields involved. It clearly distinguishes from sibling tools like asc_app_info_localization_update (app-level) and asc_beta_build_localization_update (beta-specific).

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?

The context is clear: this tool is for version/locale metadata updates, and the locale must be explicit. However, it does not explicitly name alternatives when not to use it, though the scope is evident and excludes app-level or beta-level localizations.

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