Skip to main content
Glama
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew

Delete playlist

delete_playlist
DestructiveIdempotent

Permanently delete a SoundCloud playlist by its playlist ID to remove it from your account.

Instructions

Delete a playlist permanently.

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

Input Schema

NameRequiredDescriptionDefault
playlistIdYes

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 / playlistId / minimum
      Removed value: -1
    • changedInput schema / properties / playlistId / type
      Previous value: -"number"New value: +[
      +  "string",
      +  "number"
      +]
  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 destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds only the word "permanently", reinforcing irreversibility but saying nothing about ownership/auth requirements, effect on contained tracks, or error behavior for a nonexistent or foreign playlist.

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 six-word sentence with the destructive nature front-loaded and zero padding. It is appropriately sized relative to what it conveys, though its brevity leaves meaning gaps addressed in other dimensions.

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?

For a one-parameter destructive mutation with no output schema, the definition covers the essential action and its permanence, which is the minimum an agent needs to avoid accidental data loss. It is nevertheless thin: authorization requirements, side effects on playlist tracks, and ID format are all absent.

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% for the single required playlistId parameter, and the description does not mention it at all. It neither clarifies whether the ID is the numeric playlist ID or a URL, nor what identifier forms are accepted despite the string|number 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?

"Delete a playlist permanently" names a specific verb (delete) and resource (playlist) plus the consequence, which separates it from update_playlist and remove_track_from_playlist in the sibling list. It is clear but makes no explicit sibling differentiation.

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 use this rather than update_playlist (for modifying) or remove_track_from_playlist (for removing contents), and no mention of preconditions such as owning the playlist. The agent must infer the selection criteria entirely from the tool name.

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