Skip to main content
Glama
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew

Add tracks to playlist

add_tracks_to_playlist

Append one or more tracks to an existing SoundCloud playlist by specifying the playlist ID and track IDs, so you can update playlists without recreating them.

Instructions

Append tracks to an existing playlist.

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>",
      "trackIds": "<trackIds>"
    },
    "name": "add_tracks_to_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
verboseNoReturn every field SoundCloud sends, such as descriptions, not the compact summary
trackIdsYes
playlistIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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"
      +]
    • 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

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so safety posture is covered. The description adds only that the operation is additive on an existing object, saying nothing about duplicate tracks, playlist size limits, rate limiting, or whether the response reflects the updated playlist.

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?

A single front-loaded sentence with no filler. It is efficiently written, though the brevity stems partly from under-specification rather than disciplined editing.

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

Completeness2/5

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

For a mutation tool with no output schema and a 33%-documented, partly multi-typed parameter set, one sentence is not enough. An agent lacks the duplicate-handling, permission, and return-shape context needed to call this confidently.

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

Parameters2/5

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

Schema coverage is only 33% – 'verbose' is documented in the schema, but playlistId and trackIds are not, and the description adds nothing about either. It misses the useful details an agent needs: that trackIds accepts mixed string/number IDs, that at least one must be supplied, and what verbose changes in the result.

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?

Specific verb ('append') plus resource ('tracks to an existing playlist'), which cleanly separates it from remove_track_from_playlist and update_playlist. It stops short of naming a sibling, so an agent must infer the distinction from the tool name.

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

Usage Guidelines2/5

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

No guidance on when to reach for this versus create_playlist or update_playlist, and no stated prerequisites beyond 'existing playlist'. The requirement that the caller own or have edit rights to the playlist is left entirely implicit.

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