The core pattern
Most high-signal Aria prompts share three parts:- Verb — what you want done (“plan,” “find,” “draft,” “summarize”).
- Subject — what / who / which track (“this track,” “the new release,” “my Spotify audience”).
- Constraint — how / when / for whom (“for dreampop curators,” “by next Friday,” “under $100”).
Strategy & next moves
Release planning
Track analysis
Playlist research
Pitch drafting
Artist intelligence
A&R discovery (Pro+)
Storefront
Pattern: more context = sharper answer
Open-ended works: “What do I do now, and why?” — Aria pulls your current state and recommends. More context gets sharper answers: “My release is in 3 weeks, I have a $50 budget, my last release got 8k streams. What’s the highest-impact thing to do this week?” Both work. The more constraints you supply, the more concrete the answer.Pattern: ask for strategy AND triage
Aria reads the music-business knowledge graph plus your real data, so it can do both: recommend the next move and shortlist work for you. Strategy: “What do I do this week to maximize my release momentum?” Triage: “Of these 25 playlist matches, which 3 are highest priority, and why?” Decision-level choices (e.g., signing a label deal) are still yours — Aria gives you the framing and the data.Pattern: paste, don’t paraphrase
If a curator emailed you, paste the email and ask for a draft reply. Don’t summarize — Aria sees nuance you might miss. If a curator emailed a long message, paste the whole message — let Aria spot the nuance.What Aria won’t do
- Send a message without your approval. Aria drafts; you confirm.
- Submit to Spotify editorial. No public API for that.
- Move money on your behalf. Aria can summarize earnings and flag actions, but payouts go through Stripe directly.
Related pages
- Aria overview — what Aria is
- MCP overview — the tools Aria uses