Skip to main content
Glama
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew

Get playlist

get_playlist
Read-only

Retrieve a SoundCloud playlist's details and track list by playlist ID, with an option to return full metadata or a compact summary.

Instructions

Get a playlist's details and its tracks.

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": "get_playlist"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / 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.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. Beyond that the description adds nothing: it does not say how many tracks come back, whether tracks are full objects or partial, whether pagination/next_page applies, or what the verbose flag does.

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?

A single short sentence with no wasted words, and front-loaded with the resource being fetched. It is concise to the point of being under-specified for a tool with an ambiguous sibling.

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?

There is no output schema, so the description should explain the return shape at least roughly, and it does not. It also omits how the embedded track list is truncated or paginated, which is the main thing an agent needs to know before calling.

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 50%: verbose is documented in the schema, but playlistId has no description and the description does not compensate by explaining that a string URL or numeric id is accepted. The sentence adds no parameter meaning beyond 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?

A concrete verb and resource are stated, and the description notes both playlist details and its tracks. However, it does not distinguish itself from the sibling get_playlist_tracks, which appears to return the same track data, leaving genuine ambiguity about which to call.

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?

There is no when-to-use guidance, no mention of alternatives such as get_playlist_tracks, get_my_playlists, or search_playlists, and no prerequisites. The agent must infer selection criteria entirely from the name.

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