App Store Keyword Ops

Use the Astro MCP as the metric authority and competitor-keyword source. Use app-store-scraper and aso for listing context and product-fit analysis, and helm-asc for App Store Connect reads, writes, and existing export conventions when available. Resolve identifiers from the current repository and live services; remembered app IDs, versions, locales, and metadata are leads rather than authority.

1. Resolve the target

Identify the app, bundle or App Store ID, storefronts, editable version, and requested locales from repository configuration and live App Store Connect state. Map every target locale to the Astro storefronts that its localization serves in scope. Query Astro for each mapped storefront. Do not substitute evidence from a storefront outside that mapping. Record whether each target localization exists. Record whether its keyword field is currently editable. If a target localization does not exist, stop work for that locale and report it. Do not create the localization. Default an unspecified mutation request to an audit and dry run.

If the Astro MCP is unavailable or a target locale cannot be queried, stop new-keyword selection for that locale and report the gap. Do not replace Astro observations with estimates from web search or another tool.

Complete when: the app, version, target locales, Astro locale mapping, live editability, and requested write scope are explicit and current.

2. Capture the baseline

Read the exact title, subtitle, and keyword value for every target locale. Batch reads may establish the matrix; when a batch is truncated, ambiguous, or missing any field, re-read every target locale individually and preserve explicit empty values.

For analysis, normalize keyword tokens by Unicode NFC, comma splitting, surrounding-whitespace removal, and locale-appropriate case folding. Preserve the source string separately. Audit: