Skip to main content
Glama

Set an album's running order

set_album_tracks
Destructive

Put these tracks on this album, in this order. Replaces whatever was on it. A track left out is taken off the album, not deleted.

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": {
      "album_id": "<album_id>",
      "track_ids": "<track_ids>"
    },
    "name": "set_album_tracks"
  }
}

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.
dry_runNoTrue to check the call and see what it would replace, without writing anything.
album_idYes
track_idsYesIn running order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 replacement risk is flagged structurally. The description still adds real value beyond them by clarifying the blast radius: omitted tracks are removed from the album rather than deleted from the catalog, which is exactly the distinction an agent needs before calling a destructive tool. It does not mention the available dry_run check, which is the one notable behavioral omission.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action, then the replacement consequence, then the non-destructive clarification. Nothing is wasted and each sentence carries distinct information.

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 four-parameter destructive mutation with annotations and no output schema, the description covers the essential semantics: what is overwritten and what is preserved. It is slightly incomplete in not pointing to dry_run as the safe way to preview the replacement, which matters for a destructive call.

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 coverage is 75%, with dry_run and artist already well documented in the schema. The description's 'in this order' restates what track_ids' schema text ('In running order') already says, and album_id is left undocumented in both places, so it adds little meaning beyond the structured fields.

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?

The description gives a concrete verb+resource+effect: put these tracks on this album in this order, replacing existing contents. That is specific enough to distinguish it from a metadata-editing tool like update_album, though no sibling is named to draw the boundary explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the replacement semantics (use this to define a full running order, not to append a single track), but the description never states when to prefer this over alternatives such as update_album or add_version, and gives no preconditions such as ownership or connection type.

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