Skip to main content
Glama
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew

Update playlist

update_playlist
DestructiveIdempotent

Edit a playlist's title, description, and sharing settings, or replace and reorder its entire tracklist by supplying track IDs in the desired order.

Instructions

Edit a playlist's title, description, or sharing. trackIds replaces and orders the entire tracklist.

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": {
      "playlistId": "<playlistId>"
    },
    "name": "update_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
sharingNo
verboseNoReturn every field SoundCloud sends, such as descriptions, not the compact summary
trackIdsNoReplaces the tracklist entirely, in this order
playlistIdYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.1.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / playlistId / minimum
      Removed value: -1
    • changedInput schema / properties / playlistId / type
      Previous value: -"number"New value: +[
      +  "string",
      +  "number"
      +]
    • addedInput schema / properties / trackIds / description
      Added value: +"Replaces the tracklist entirely, in this order"
    • changedInput schema / properties / trackIds / items / type
      Previous value: -"number"New value: +[
      +  "string",
      +  "number"
      +]
    • addedInput schema / properties / verbose
      Added value: +{
      +  "default": false,
      +  "description": "Return every field SoundCloud sends, such as descriptions, not the compact summary",
      +  "type": "boolean"
      +}
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=true but do not say what is destroyed; the description fills that gap by warning that trackIds replaces and re-orders the entire tracklist. No annotation is contradicted, though authentication/ownership requirements and error behavior remain undisclosed.

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?

Two short sentences, zero filler: the editable fields come first and the destructive trackIds mechanic is called out second. Every clause carries information an agent needs before calling.

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

Completeness3/5

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

For a destructive, open-world mutation the description covers the key hazard (full tracklist replacement) and the editable surface, which is adequate but has clear gaps. It says nothing about the sharing enum values, ownership/permission requirements, or what a partial update returns.

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 only 33% (trackIds and verbose are documented; title, description, sharing, playlistId are not), and the description compensates by naming the three metadata fields it can change and explaining the replace-and-order semantics of trackIds. The playlistId target and verbose flag are left to the schema.

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 ('Edit a playlist') and names the concrete editable fields (title, description, sharing), plus the discrete tracklist-replacement behavior. Its mention that trackIds replaces the whole tracklist implicitly separates it from add_tracks_to_playlist and remove_track_from_playlist, though no sibling is named outright.

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 only implied: the 'replaces the entire tracklist' phrasing signals that this tool is not for incremental track additions, but the description never says when to prefer add_tracks_to_playlist/remove_track_from_playlist/delete_playlist instead, nor any prerequisites such as playlist ownership.

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