Skip to main content
Glama
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew

Get track comments

get_comments
Read-only

Retrieve comments on a SoundCloud track with their audio timestamps, so you can review listener feedback at specific moments. Set a limit or request full fields as needed.

Instructions

Get comments on a track, with their timestamps into the audio.

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_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
trackIdYes
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. Changed7 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"
    • removedInput schema / properties / trackId / minimum
      Removed value: -1
    • changedInput schema / properties / trackId / 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"
      +}
    • 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

B3/5.0
Behavior3/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 externally. The description contributes the useful behavioral detail that returned comments carry audio-relative timestamps, but it omits pagination behavior (default 50, cap 200) and what the verbose flag expands, which are the traits that actually affect how an agent calls it.

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 padding; the core resource and the notable return characteristic both land immediately. Brevity here is efficient rather than under-specified for the purpose statement itself.

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

Completeness3/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 detail is not required, and the tool is simple (one required param). Still, with two of three parameters undocumented in both schema and prose and no paging guidance, an agent lacks enough to call it confidently for anything beyond the default single fetch.

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%: only 'verbose' is documented in the schema, while trackId and limit carry no description. The prose mentions no parameters at all, so it does not compensate for the gap or explain accepted id forms (string or number) or the limit ceiling.

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?

States a specific verb and resource ('Get comments on a track') and adds a distinguishing detail about the payload ('timestamps into the audio'). It is clearly separable from mutating siblings like add_comment, but it never explicitly contrasts with other read tools such as get_track.

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 use this versus alternatives, no prerequisites, and no mention of how to page through results even though a limit parameter with a 200 maximum exists. The agent must infer all usage context from the name alone.

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