Skip to main content
Glama
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew

Search playlists

search_playlists
Read-only

Find SoundCloud playlists by keyword to discover collections matching a topic, artist, or mood. Set a result limit or request full details as needed.

Instructions

Search SoundCloud playlists by keyword.

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": {
      "query": "<query>"
    },
    "name": "search_playlists"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
next_hrefNoNext page URL; pass to next_page
collectionYesPage items

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"
    • addedInput schema / properties / limit / default
      Added value: +50
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / query / minLength
      Added value: +1
    • addedInput schema / properties / verbose
      Added value: +{
      +  "default": false,
      +  "description": "Return every field SoundCloud sends, such as descriptions, not the compact summary",
      +  "type": "boolean"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "properties": {
      +    "collection": {
      +      "description": "Page items",
      +      "items": {},
      +      "type": "array"
      +    },
      +    "next_href": {
      +      "description": "Next page URL; pass to next_page",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "collection"
      +  ],
      +  "type": "object"
      +}
  2. First observedv1.0.0

TDQS

C2.7/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, but the description adds nothing beyond that. It says nothing about result ordering, pagination behavior, result-count limits, or what the verbose flag changes in the payload.

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 zero filler and no redundancy, which is appropriate in form. Its brevity is the right shape, though it is under-specified rather than merely concise.

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?

An output schema exists, so return-value fields need not be explained, but for a three-parameter open-world search tool the definition leaves the agent without paging guidance, limit semantics, or any routing versus search_tracks/search_users. The complexity warrants more than one clause.

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 description coverage is only 33%: verbose is documented in the schema, while query and limit have no descriptions at all. The phrase 'by keyword' only loosely hints that query is a free-text string and gives no meaning for limit's 1-200 range or default of 50, so the description fails to compensate for the gap.

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 specific verb plus resource ('Search SoundCloud playlists') and a scope qualifier ('by keyword'), which cleanly separates it from siblings such as search_tracks and search_users by the resource noun alone. It stops short of naming an alternative explicitly, so a 4 rather than a 5.

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 guidance on when to use this search versus browsing with get_user_playlists or get_playlist, and no mention of how to page results despite a next_page sibling existing. The only implied usage cue is 'by keyword', which merely restates the required query parameter.

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