When to use it
- You have many keyword opportunities and want fewer, strategy-sized buckets.
- You need a single “start here” group (
prioritizeClusterIdin the API response). - You are aligning copy, screenshots, and keyword field around consistent user intents.
How it works (short)
- The brief loads keyword opportunities for the app.
- With
intentClusters=1, those keywords are analyzed and split into a small number of intent groups. - Each group gets a label (typically the strongest opportunity keyword in that group) and avgOpportunityScore.
- The brief adds an
intentClustersobject and usually a prioritized action like “Prioritize this intent group: …”.
API
Use the same endpoint as the brief:intentClusters=1ortrue— enable clustering (+2 credits on top of the brief base cost × country multiplier).countries=us,gb,de— multi-country brief; clustering runs per country (each storefront can have different opportunity mixes).
MCP
Tool:aso_brief
| Argument | Description |
|---|---|
intent_clusters | true to enable semantic intent clustering (maps to intentClusters query) |
countries | Optional comma-separated ISO codes for multi-country briefs |
Authorization: Bearer <api-key>).
See also
- ASO Decision Brief — main orchestration endpoint
- Keyword opportunities — source keywords for clustering
- MCP Server —
aso_brieftool reference

