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

appstore-connect-mcp

by tomoki013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

[Destructive/Release] Submit an App Store version for review

asc_submit_for_review

Submit an app version for App Review. Runs preflight checks and requires explicit user confirmation before changing App Store state.

Instructions

DESTRUCTIVE / RELEASE-CLASS. Submits a version for App Review via the current ReviewSubmission API — this changes real, public-facing App Store state and cannot be trivially undone. Always runs asc_release_preflight first and refuses to proceed if any check fails. Always shows a native macOS confirmation dialog (with the preflight summary) to the human user and never submits silently just because it was called; it only proceeds if the human explicitly clicks Submit.

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

Input Schema

NameRequiredDescriptionDefault
appIdYesBundle id, app name, or App Store Connect app id
versionYesApp Store version string, e.g. "1.1"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.5/5.0
Behavior5/5

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

Despite no annotations, the description discloses irreversible state changes ('cannot be trivially undone'), mandatory preflight dependency, automatic refusal on check failure, and the always-required native confirmation dialog. It even explains the tool will not act silently even if called, which is critical for an agent to anticipate.

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 dense paragraph that front-loads the destructive warning and packs the action, preflight, and confirmation into efficient sentences with zero redundancy.

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

Completeness5/5

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

Given the tool's high complexity (destructive, no output schema, no annotations), the description covers the action, safety dependencies, and user-interaction requirements. It provides sufficient context for an agent to understand the tool's role and invocation constraints, including the preflight prerequisite and refusal behavior.

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 covers 100% of parameters with descriptions, so the description's lack of parameter detail is acceptable. No additional semantics beyond what the schema provides; baseline 3 applies.

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 'Submits a version for App Review via the current ReviewSubmission API' with a specific verb and resource. The 'DESTRUCTIVE / RELEASE-CLASS' prefix and reference to preflight distinguish it from sibling tools like asc_version_create or asc_submission_status.

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?

Explicitly instructs 'Always runs asc_release_preflight first and refuses to proceed if any check fails,' providing a clear prerequisite and execution order. It also notes it 'never submits silently' and requires human confirmation, guiding when the agent should invoke 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