LocalASOMCP and AI agents
LocalASO listing_get tool: read your saved App Store listing
listing_get returns the saved App Store listing of an app in its main locale: name, subtitle, keyword field, promotional text and description. An agent uses it to ground keyword suggestions in what your page already says.
Updated
Input
| Argument | Type | Required | Meaning |
|---|---|---|---|
app | string | yes | Internal id, App Store trackId, or part of the app name |
Output
An object with app (the usual summary) and listing:
| Field | Meaning |
|---|---|
locale | The App Store locale, such as en-US or de-DE |
name | The app name |
subtitle | The subtitle |
keywords | The keyword field, comma separated |
promoText | The promotional text |
description | The description |
whatsNew | What's New text, present for some listings |
source | Where the text came from: public (the public store page), asc (App Store Connect) or draft (a draft saved in LocalASO) |
keywordsDerived | true when the keyword field was derived from the name, subtitle and description because no App Store Connect key was available |
updatedAt | When the listing was last saved |
The source and keywordsDerived fields matter. When no App Store Connect key is available, the keyword field is derived from the other text, so it can differ from the field you actually saved. An agent that does not read these flags may treat a derived guess as your actual keywords.
Apple's limits an agent should check against
Ask the agent to count before it suggests text. The limits, from Apple's documentation: name and subtitle 30 characters each, the keyword field 100 bytes, promotional text 170 characters and the description 4,000 characters. Non-Latin characters take more than one byte in the keyword field, so a Japanese list holds fewer characters than an English one. You can double-check any suggestion with the character counter and the keyword field checker.
Example prompts
These are examples, not recorded output.
- "Read my listing with listing_get and tell me which words from my top-ranked keywords are missing from the name and subtitle." The agent compares
listingwith the result of board_get. - "Is my keyword field repeating words from the name?" The agent compares
keywordswithnameandsubtitle, and should mention ifkeywordsDerivedis true. - "Suggest a subtitle under 30 characters that includes my best Push keyword." The agent proposes text and counts its length.
What it does not do
- It returns one locale, the app's main one. For other languages, use the localization workflow in the app; see App Store localization.
- It is read-only. The MCP server has no write tool for listings and cannot upload anything to App Store Connect, so every change goes through you.
- Like all tools, it returns a message instead of data when the Mac has no valid license.
Next step
Pair it with competitors_get to compare your page with those ahead of you, or see the whole tool set in the MCP docs. For writing the fields, the title and subtitle guide is the next read.
Questions
- Can listing_get return a locale other than the main one?
- No. It returns the listing of the app's main locale only.
- Can an agent change my listing through MCP?
- No. There is no write tool for listings, and the MCP server cannot upload to App Store Connect.
Sources
- Apple: developer.apple.com/help/app-store-connect/reference/app-information/app-information#name (checked November 1, 2026)
- Apple: developer.apple.com/help/app-store-connect/reference/app-information/app-information#subtitle (checked November 1, 2026)
- Apple: developer.apple.com/help/app-store-connect/reference/platform-version-information#keywords (checked November 1, 2026)
- Apple: developer.apple.com/help/app-store-connect/reference/platform-version-information#promotional-text (checked November 1, 2026)
- Apple: developer.apple.com/help/app-store-connect/reference/platform-version-information#description (checked November 1, 2026)
Do this for every country, in minutes