Skip to main content
Glama
crates-music-mcp

crates-music-mcp

by guohangbk

delete_playlist

Permanently deletes a user-created playlist on QQ Music, NetEase Cloud Music, or Kugou; call without confirm to verify the playlist name, then set confirm=true to execute.

Instructions

删除一个自建歌单(不可逆)。

playlist_id 用 my_playlists 返回的 id(三平台已统一:QQ 的 dirid、 网易云的 id、酷狗的 listid 都放在这个字段里)。 必须传 confirm=True 才会真的执行;先不带 confirm 调用可查看歌单名做二次确认。

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": {
      "service": "<service>",
      "playlist_id": "<playlist_id>"
    },
    "name": "delete_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
serviceYes
playlist_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so: it declares destructive/irreversible behavior, discloses that the default is a non-destructive dry-run, and explains the confirm gate. It does not mention permissions/credential requirements or any rate limiting, which is the remaining gap.

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?

Three tightly structured bullets: scope/risk, id provenance, confirm protocol. Every point earns its place, though the parenthetical platform mapping is dense detail that could partly live in schema.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, three-parameter tool with an output schema, the description covers the safety-critical facts an agent needs: irreversibility, the confirm gate, and where the id comes from. Only authentication/prerequisite context is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does for two of three parameters: playlist_id provenance is spelled out per platform (QQ dirid, NetEase id, Kugou listid), and confirm's default-false preview semantics are explained. The service parameter's meaning is only conveyed via the Platform $defs entry, not in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('删除一个自建歌单') and immediately scopes it to user-created playlists, which distinguishes it from the create_* and playlist_songs siblings. The irreversibility note is front-loaded in the same sentence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Prescribes an explicit workflow: call once without confirm to preview the playlist name for secondary verification, then call with confirm=True to execute. It also names my_playlists as the required source of playlist_id, so the agent knows the prerequisite step. This is well beyond implied usage.

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