Skip to main content
Glama
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew

Get stream URL

get_stream_url
Read-only

Retrieve temporary audio URLs for SoundCloud tracks: HLS for full tracks and MP3 for previews; blocked tracks return no stream.

Instructions

Get temporary audio URLs: HLS for full tracks, MP3 for previews. Blocked tracks have no stream.

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": {
      "trackId": "<trackId>"
    },
    "name": "get_stream_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / trackId / minimum
      Removed value: -1
    • changedInput schema / properties / trackId / type
      Previous value: -"number"New value: +[
      +  "string",
      +  "number"
      +]
  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 already declare readOnlyHint and openWorldHint, so the bar is lower, and the description still adds real behavioral context: URLs are temporary and blocked tracks yield no stream at all. That 'no stream' case is exactly the kind of edge-condition disclosure an agent needs to handle a null-like result, though the lifetime of 'temporary' is not quantified.

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 with the core capability front-loaded and zero redundant wording. Nothing could be removed without losing information.

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

Completeness4/5

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

With only one parameter, no output schema, and rich annotations, this is close to complete: it covers both output formats and the blocked-track case. It could go further by hinting at expiry duration or the response field shape, but a correct call is derivable from what is present.

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?

Schema description coverage is 0% for the single trackId parameter, and the description says nothing about its expected form, even though the schema allows either string or number. The parameter name is largely self-explanatory, so this is not fatal, but the description adds no meaning beyond the schema here.

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 states a specific verb and resource ('Get temporary audio URLs') and explains the two format outcomes (HLS for full tracks, MP3 for previews), which lets an agent distinguish it from a generic URL tool. It stops short of explicitly contrasting itself with the sibling resolve_url, so it falls just under the top mark.

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: an agent must infer that this is the tool to call when it needs playable audio for a known track id. There is no statement of when to prefer this over resolve_url, nor any prerequisite or when-not guidance.

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