Prepare a release, as a draft
save_release_draftWrite the release details for a track or album as a DRAFT. A draft costs nothing, can be changed and goes nowhere until the artist says so. Returns a draft_hash identifying exactly what you prepared, and release_rules: everything the track or album still needs to meet the stores' rules (master format, cover, sub-genre, languages, countries, performer roles) before it can be submitted. An older track or album usually needs some of it. A draft saves even when it is unfinished: a release date sooner than the stores take is saved and comes back in warnings, and submitting refuses it until it is changed.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"type": "<type>",
"item_id": "<item_id>"
},
"name": "save_release_draft"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | ||
| artist | No | Only when you are connected as a label: the roster artist this call is for — their artist_user_id from list_roster, or their exact artist name. Required for every artist tool on a label connection. Leave it out on an artist's own connection. | |
| item_id | Yes | The track's or album's id. | |
| release | No | The release fields, by the names get_requirements(entity: "release") gives them, for example { "release_type": "single", "scheduled_date": "2026-11-20", "description": "...", "pitching_directly": "...", "release_timeline": "...", "artist_quotes": "..." }. Add "splits" for royalty splits. Send only what you are setting. |