Skip to main content
Glama
Sign In
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Remove playlist repost

unrepost_playlist
Idempotent

Removes a reposted playlist from your SoundCloud profile by playlist ID, so you can undo a reshare and keep your feed current.

Instructions

Remove a repost of 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": "unrepost_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
playlistIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.2

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the safety profile is fully covered. The description adds nothing beyond this — no auth requirements, no note that repeat calls are safe (already in idempotentHint), and no clarification of the effect on repost counts or feed visibility.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of waste, which is good, but its brevity leaves the definition under-specified for a mutation tool. Appropriateness of size is borderline given the missing prerequisite and parameter context.

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?

The rich annotation set covers the safety semantics, and no output schema exists, so the remaining burden is the undocumented playlistId and the lack of any usage condition. For a one-parameter toggle tool this is minimally sufficient but not complete.

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 0% and the description only implies that the sole parameter identifies a playlist. It does not explain that playlistId accepts a string or number, what identifier form is expected, or add any meaning beyond the schema's type union.

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 ('Remove') and resource ('a repost of a playlist'), making the inverse of repost_playlist unambiguous. It stops short of naming the sibling to use for the opposite action, so an agent must infer the pairing from the tool name alone.

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 when-to-use guidance, no prerequisites, and no mention of the alternative (repost_playlist) or of what happens when the playlist was never reposted. The only implied usage is a restatement of the tool name.

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