Skip to main content
Glama
Sign In
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get playlist reposters

get_playlist_reposters
Read-only

Retrieves the users who reposted a given SoundCloud playlist; set a limit or enable verbose mode to inspect reposter details.

Instructions

List the users who reposted a playlist.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
next_hrefNoNext page URL; pass to next_page
collectionYesPage items

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.2

TDQS

C2.9/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 descriptive burden is low, but the description adds nothing beyond the name: no note on pagination via limit, no sense of result volume (up to 200), and no statement that it reads public repost data. It is a restatement rather than added behavioral context.

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 filler, which is appropriate. Its brevity edges toward under-specification rather than waste, but nothing is redundant.

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 values need not be described, but for a three-parameter paged list tool the description omits pagination behavior, the numeric/string ID flexibility, and how results relate to next_page. That leaves the agent short of what it needs to call it confidently.

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. The description does not compensate by explaining playlistId (accepts string or number) or what limit controls and how it interacts with paging. Two of three parameters carry no meaning anywhere.

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 (List) and a precise resource (users who reposted a playlist), which is enough to separate it from the neighboring get_track_reposters and get_user_reposts. It does not however explicitly name those siblings to reinforce the distinction.

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?

The purpose implies when the tool applies (inspecting a playlist's reposters), but there is no explicit when-to-use or when-not-to-use guidance, and no mention of the closely related get_track_reposters, repost_playlist, or next_page alternatives.

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

Deploy Server

Other Tools