Skip to main content
Six 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.

Run a weekly ASO review

Exercises portfolio, actions_summary and visibility_history.

Triage this week’s keyword losses

Exercises list_keywords, ranking_history and serp_movers.

Explain why a keyword moved

Exercises ranking_history, serp_snapshot and changes_timeline.

Compare against a competitor in one market

Exercises app_summary, serp_snapshot and visibility_history.

Check whether another market fits the budget

Exercises daily_budget and list_keywords. Budget arithmetic is the one place an agent is genuinely better than the dashboard, because it can reason about a change you have not made yet. See The daily pipeline and rate limits.

Draft the next metadata iteration

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.

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.
  • 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.
Last modified on July 31, 2026