build-campaign
Spotify Ads API — Full Campaign Builder
Given a plain-text description of an advertising campaign, parse it into structured API calls and create the full campaign hierarchy: Campaign → Ad Sets → Ads.
Default Flow: Draft → Validate → Publish
By default, use the draft workflow for all campaign hierarchy creation. This creates draft entities first, validates the entire hierarchy, and only publishes after confirmation. Route to the /spotify-ads-api:drafts build <description> skill to execute the draft flow.
The draft flow is preferred because:
- Batch validation catches all errors across the hierarchy before anything goes live
- Safe iteration — the user can review and edit drafts before publishing
- Easy undo — delete the draft if something looks wrong; no live entities to clean up
Publishing a draft always requires explicit user confirmation immediately before the PUBLISH request, even when auto_execute is enabled.
Only use the direct creation flow below if the user explicitly asks to skip drafts or create live entities immediately. If a direct write is denied, do not infer that the credentials are read-only; offer the draft workflow instead.