Skip to main content
Glama

Set who a track is billed to

set_track_artists
Destructive

Replace who a track is billed to: the "Artist & Guest feat. Guest" line on every store. Send the whole list in billing order, as the artist tells you, with at least one primary. Nobody is added for you: the account's own artist is on the list only if you send it, so ask, and Send refuses a song with no primary artist. primary and with make up the main credit; featured and remixer become the "feat." part. A primary artist besides the account's own is a collaboration: ask the artist whether they have all the rights needed for it, and send rights_confirmed: true only when they say yes. Without it the call is refused and nothing is written. A song billing two or more names also needs each credited with set_track_credits under that name with a real role. The songwriter, performer and producer credits are a different list, set with set_track_credits.

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": {
      "track_id": "<track_id>",
      "artists": "<artists>"
    },
    "name": "set_track_artists"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
artistsYesEveryone billed, in billing order. An empty list clears the billing: the song then has no billed artist.
dry_runNoTrue to check the call and see what it would replace, without writing anything.
track_idYes
rights_confirmedNoRequired as true when the list has a `primary` artist besides the account's own. Ask the artist first, in these words: "I have all the rights needed for this collaboration". Send true only when they confirm it. Never assume it: it is recorded as their legal confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / artists / description
      Previous value: -"The artists besides the account's own, in billing order. An empty list clears the billing back to the artist's own name."New value: +"Everyone billed, in billing order. An empty list clears the billing: the song then has no billed artist."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description goes well beyond that by disclosing that the whole billing line is replaced, that a refused call writes nothing, and that rights_confirmed is recorded as the artist's legal confirmation. These are exactly the side-effect and validation semantics an agent needs before invoking a destructive write.

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

Conciseness3/5

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

The operation and its constraint are front-loaded in the first two sentences, which is good. However, the prose becomes cramped and repetitive — set_track_credits is referenced twice in the closing sentences, and the phrase "ask, and Send refuses..." is awkwardly compressed, costing readability in an otherwise dense block.

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?

Given a destructive 5-parameter write with no output schema, the description covers preconditions, legal confirmation, cross-tool dependencies and ordering rules thoroughly. The main gap is what a successful call returns or how the replaced billing reads afterward, which would help an agent confirm the change.

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

Parameters4/5

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

Schema coverage is 80% so the parameters are already largely documented, but the description adds real meaning: list order is billing order, at least one entry must be `primary`, and roles map to output semantics (primary/with form the main credit, featured/remixer become the feat. part). That role interpretation is not derivable from the bare enum in the schema.

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

Purpose5/5

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

States a specific mutating verb plus resource ("Replace who a track is billed to") and immediately scopes it to the store-visible billing line. It also explicitly distinguishes itself from set_track_credits ("The songwriter, performer and producer credits are a different list"), so an agent can pick between the two without opening either schema.

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

Usage Guidelines5/5

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

Gives concrete when-to-use instructions: ask the artist about the account's own artist because nobody is auto-added, ask about rights and send rights_confirmed:true only on explicit confirmation, and hand off songwriter/performer/producer work to set_track_credits. It also names the failure conditions (no primary, missing rights confirmation) that select a different path.

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