Skip to main content
Glama

Prepare a release, as a draft

save_release_draft
Destructive

Write 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

NameRequiredDescriptionDefault
typeYes
artistNoOnly 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_idYesThe track's or album's id.
releaseNoThe 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is known; the description adds real value on top by stating that drafts are non-final, changeable, and never published, and by describing return payloads (draft_hash, release_rules) and the partial-save/warnings behavior for invalid dates. It does not contradict the destructive annotation — a draft write is still a write — but it also doesn't spell out any permission/auth requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and the draft scope, then builds out returns and the edge case. Sentences carry distinct information, though the final sentence about release dates and warnings is dense and could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter, nested-object write tool with no output schema, the description covers purpose, the two return values, and the key edge case (invalid date saved but refused at submit). What is missing is minor: no mention of failure modes beyond the date case, and no pointer to how the draft is later submitted.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 75%, so the schema already carries most parameter meaning, including the artist/connection rule and the release object. The description itself adds no parameter-level detail beyond pointing at get_requirements for field names, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with a clear scope qualifier: "Write the release details for a track or album as a DRAFT." The draft framing separates it from submission/finalization tools, though it does not name a specific sibling to contrast with (e.g. the submit/finalize path).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"A draft costs nothing, can be changed and goes nowhere until the artist says so" plus "An older track or album usually needs some of it" gives clear context for when to reach for this tool and reassures the agent that partial data is acceptable. It stops short of naming alternatives or exclusions (e.g. when to call get_requirements or check_readiness first instead).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources