Skip to main content
Glama
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew

Create playlist

create_playlist

Create a new SoundCloud playlist with optional tracks, title, and description; keep it private by default or choose public sharing.

Instructions

Create a playlist with optional tracks. Private by default.

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": {
      "title": "<title>"
    },
    "name": "create_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
sharingNoprivate
verboseNoReturn every field SoundCloud sends, such as descriptions, not the compact summary
trackIdsNo
descriptionNo

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"
    • addedInput schema / properties / sharing / default
      Added value: +"private"
    • addedInput schema / properties / title / minLength
      Added value: +1
    • 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.6/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 the safety profile is largely covered. The description adds that the playlist is private unless specified, a useful behavioral default, but it does not state authentication prerequisites, whether the created playlist is returned, or what happens with invalid trackIds.

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, front-loaded with purpose and the default behavior. No filler.

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 5-parameter mutation tool with only 20% schema coverage and no output schema, the description does not explain required title semantics, verbose mode, or the expected return. Auth requirements from sibling tools like connect_soundcloud and auth_status are also unmentioned.

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?

With 20% schema description coverage, the description only lightly compensates: 'optional tracks' maps to trackIds and 'private' maps to sharing. It does not document the verbose flag, the description field, or acceptable trackId formats, leaving several parameters under-specified in both schema and description.

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?

The description states a specific verb+resource ('Create a playlist') and clarifies optional tracks and the private default. Sibling tools such as update_playlist, add_tracks_to_playlist, and delete_playlist are readily distinguished; this is the creation entry point.

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?

'Optional tracks' implies it can seed a playlist at creation, and 'private by default' hints at sharing behavior, but there is no explicit when-to-use guidance or exclusion versus add_tracks_to_playlist for adding tracks later. The agent must infer the workflow.

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