Skip to main content
Glama
Sign In
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Repost playlist

repost_playlist
Idempotent

Repost a SoundCloud playlist to your followers by passing its playlist ID, enabling sharing from your account.

Instructions

Repost a playlist to the user's followers.

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

Input Schema

NameRequiredDescriptionDefault
playlistIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.2

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds one meaningful behavioral fact — that the repost is broadcast to the user's followers — but says nothing about auth requirements, error behavior on repeated reposts, or what the call returns.

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?

One short, front-loaded sentence with no filler; nothing is wasted. It is concise to the point of being thin, but the structure is sound.

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?

This is a simple one-parameter mutation with no output schema, so the description need not explain return values. However, given annotations only cover safety hints, the missing input format guidance and lack of any when-to-use context leave real gaps for an agent acting on a public-visible write.

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 0% for the single required parameter, and the description adds no meaning: it never says whether playlistId is a numeric ID, a permalink, or a URL (the sibling resolve_url hints that URL/ID ambiguity matters). The schema itself allows string or number with no description, so the ambiguity is left unresolved.

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 ('Repost') and resource ('a playlist'), and the target audience ('to the user's followers') is a useful scope detail. It does not differentiate from siblings such as repost_track or unrepost_playlist, but the action itself is unambiguous.

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 repost versus when to use unrepost_playlist or repost_track, nor any precondition such as needing an authenticated session. The agent must infer usage entirely from the name and annotations.

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