Skip to main content

Spotify Ads from Chat: Pick the Account, Then Run Audio Campaigns with AI

· 3 min read
MCPBundles

TL;DR

  • Spotify Ads on MCPBundles now resolves ad accounts by brand name, remembers your pick for the thread, and exposes read paths for pulse, approvals, and exports without a separate “find the UUID” step.
  • You can name campaigns, ad sets, and ads in chat, pull last week’s metrics for one campaign, and draft a paused ad set (UK geo, daily budget, delivery off) before anything goes live.
  • Planning defaults stay conservative: paused campaigns, delivery off on new ad sets and ads until you mean to launch.
  • I wrote this for podcast and brand teams who already buy on Spotify and hate opening Ads Manager for a five-minute standup answer.

Three Spotify brands, one login, standup in ten minutes. “Anything stuck in approval?” shouldn’t cost you four clicks and a prayer you didn’t pause the wrong row.

I talk to marketers who run Spotify alongside everything else. None of them complain that Ads Manager lacks buttons. They complain about the ladder — business, ad account, campaign, ad set, ad — when the question is already halfway up the tree.

Last month we shipped name-based account pick on MCPBundles for Spotify. Say Northwind Audio. If there’s one match, chat stays on that account. If two Harbors collide, you choose. I’d rather wait on you than watch a model guess.

That sounds small. It isn’t. Most “Spotify questions” die in navigation before anyone reads a number.

Once the account sticks, the boring standup stuff is actually boring in a good way. Paused lines that still spent. Ads sitting in approval. A test flight that must not serve on Saturday because someone toggled delivery while tweaking copy. Spotify’s own planning guidance treats delivery-off as normal while creative is in flux; we mirrored that in the product defaults instead of treating it as an advanced setting buried in docs.

Name the campaign the way you’d say it in standup — summer podcast test — and chat can find it without you copying IDs from a table. Same for ad sets and ads when creative ops asks “which line is stuck?” Performance for a single flight is one ask: last seven days plus lifetime, not a reporting worksheet you assemble by hand. When you’re ready to add structure, you can draft an ad set body paused with delivery off, tune geo and budget in chat, then create only when the plan looks right.

Reports are the other time sink. Quick windows should not become spreadsheet archaeology. Aggregate reads cover “how did last week look?” Async CSV jobs still exist for the finance person who wants the file — but chat can poll and show a preview instead of handing you a URL and a shrug.

Reserved podcast and music buys are their own beast — fixed CPM, lifetime budgets, forecast gates. We exposed reserved pricing lookup so you can see the rate before you commit structure. Spotify still gets the final word on eligibility; we’re not pretending otherwise.

If you live in this world, connect Spotify on MCPBundles and open the same assistant you already use for Google or Meta questions. Lead with the brand and the standup sentence — not the hierarchy.

The thread keeps context. You stay on the problem that interrupted your morning.