MCP recipes - AsoBeast

Nine prompts that produce useful answers, each with the tools it exercises. Naming the app, the market and the window is what separates a good answer from a vague one. The last two change things, so they need a token with the write scope.

Run a weekly ASO review

Give me a weekly ASO review. Start with the portfolio roll-up, then the action summary,
then visibility over the last 14 days for any app that lost ground. Tell me the single
thing to do first and why.

Exercises portfolio, actions_summary and visibility_history.

Review last month’s Action Center work

Summarize my Action Center work over the last 30 days: how many actions opened, how many
I marked done, how many resolved on their own and how many were confirmed fixed. Then list
the actions that are done, open each one and tell me which outcomes improved, which
worsened and which are still being measured, with the before and after values.

Exercises actions_activity, list_actions and get_action. An outcome is a measured change in the rule’s metric between the day you closed the action and the latest check, not proof that your change caused it. See Work the Action Center.

Triage this week’s keyword losses

For app <id>, list the tracked keywords in the us storefront whose position fell over the
last 7 days. For each, say whether the SERP itself shifted or only my position did.

Exercises list_keywords, ranking_history and serp_movers.

Explain why a keyword moved

Keyword <id> dropped this week. Show its position history for the last 30 days, the most
recent SERP snapshot, and any change events on the app in that window. Then give me the
two most likely explanations.

Exercises ranking_history, serp_snapshot and changes_timeline.

Compare against a competitor in one market

Compare app <id> with the top ranked competitor on keyword <id> in Germany. Use the SERP
snapshot for who is ahead, and visibility history for the trend over 30 days.

Exercises app_summary, serp_snapshot and visibility_history.

Ask why a competitor outranks you

For app <id>, find the keyword gaps in the comparison, then explain for the top one
why the competitor ranks above me and which of my listings could hold the keyword.

Exercises keyword_comparison and keyword_breakdown. Pass the keywordId of a gap row to keyword_breakdown and read standing for your app and insight for each competitor above you. The breakdown reads stored data only. See Why does a competitor rank above you?.

Choose which competitors to track

For app <id>, list the suggested competitors and explain in one line why each one is
worth watching. Recommend three and wait for my approval, then add them.

Exercises competitor_suggestions and, with a write token, add_competitor. Listing the suggestions spends one store lookup for the similar apps, and each add spends one competitor add. See Suggested competitors.

Draft the next metadata iteration

For app <id>, show the metadata audit and the latest ASO audit, then pull keyword
suggestions from the competitors strategy. Propose a title and subtitle that stay inside
the character limits and cover the highest opportunity uncovered keywords.

Exercises metadata_audit, app_audit and keyword_suggestions. The server cannot apply a draft, and neither can asobeast. Every metadata change is published by you in App Store Connect or Google Play Console. See Optimize listing metadata.

Track the best suggestions in one market

For app <id>, pull keyword suggestions from the competitors strategy, drop the ones I
already track in the de storefront, and show me the five with the best opportunity. Wait
for my approval, then track them in de.

Exercises keyword_suggestions, list_keywords and, with a write token, track_keywords. Each phrase you start tracking queues a first position check ahead of its store scoring job and joins the daily ranking run, so add the few that matter. Read app_run_status until its state is complete before you read the new positions. Tracking counts against your plan’s keyword market limit. See Countries and markets.

Decide where to track next

For app <id>, list the markets its listing languages suggest that I do not track yet,
with what each would cost a day. Recommend two and wait for my approval, then track
the five phrases of my title that fit best in each.

Exercises market_suggestions, get_app and, with a write token, track_keywords. A suggestion says which storefronts read a language your listing ships, not whether the app is published there. To seed a market from its own listing, use the countries step of the guided setup instead. See How do you add a market?

Close the actions you have already handled

List the open actions for app <id>. For each one that my last release already covers, say
why and wait for my yes. Then mark those done with a note naming the release.

Exercises app_actions, get_action and, with a write token, set_action_status. Marking an action done starts the measurement of its outcome, and the change appears in the history under the name of the person who minted the token. See Work the Action Center.

Writing better prompts

Three habits do most of the work.

Name the app and the market. Keywords are per storefront, so an unqualified question makes the agent guess.
Give a window. last 30 days maps directly onto the from and to parameters, which must be real dates in order. See API conventions.
Ask for the reasoning. The tools return evidence, so asking the agent to show its arithmetic makes a wrong answer visible rather than plausible.

MCP tool reference

Every tool and its parameters.

Work the Action Center

Where the prioritized queue comes from.

​Run a weekly ASO review

​Review last month’s Action Center work

​Triage this week’s keyword losses

​Explain why a keyword moved

​Compare against a competitor in one market

​Ask why a competitor outranks you

​Choose which competitors to track

​Draft the next metadata iteration

​Track the best suggestions in one market

​Decide where to track next

​Close the actions you have already handled

​Writing better prompts

​Related