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

appstore-connect-mcp

by tomoki013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

[Write] Update TestFlight "What to Test" notes

asc_beta_build_localization_update

Update the What to Test notes shown to testers for a beta build in a specific locale. Use after the localization exists to communicate testing details.

Instructions

Write. Updates the "What to Test" notes shown to testers for a build/locale. The localization must already exist for that locale (Apple creates these automatically after processing) — use asc_beta_build_localization_get to check first.

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>",
      "buildId": "<buildId>",
      "locale": "<locale>",
      "whatsNew": "<whatsNew>"
    },
    "name": "asc_beta_build_localization_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesBundle id, app name, or App Store Connect app id
localeYesLocale to update, e.g. "en-US"
buildIdYesBuild id or build/version number
whatsNewYesWhat to Test notes shown to testers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It reveals an important prerequisite (localization must exist) and Apple's automatic creation behavior. However, it does not mention what happens if the localization does not exist, whether the update is idempotent, or any permission requirements. This is decent but not comprehensive.

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 two sentences, front-loaded with the operation type ('Write') and a clear action. No unnecessary information, every sentence contributes useful context.

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 moderate complexity (4 required params, no output schema, no annotations), the description covers the essential behavior and key prerequisite. It lacks details on return values or error handling, but those are less critical for a simple update operation. The pointer to the get tool helps complete the workflow context.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds some context by tying the 'locale' parameter to the prerequisite that localization must already exist, but it doesn't add substantial meaning beyond the schema descriptions.

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 tool's function: 'Updates the "What to Test" notes shown to testers for a build/locale.' It uses a specific verb ('Updates'), identifies the resource (build/locale localization), and explicitly differentiates from the sibling tool asc_beta_build_localization_get by directing users to check existence first.

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 description gives explicit usage context: the localization must already exist, and points to asc_beta_build_localization_get as a prerequisite check. It does not explicitly list situations where the tool should not be used, but the guidance is sufficient for most agents.

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