crates-music-mcp

by guohangbk

Overview Schema Source Related Servers Discussions Admin

Python

Local

create_ncm_playlist

Creates a NetEase Cloud Music playlist by searching for specified songs and adding them to a new playlist.

Instructions

Create a real Netease Cloud Music playlist.

Same arguments and same contract as create_qq_playlist; songs are resolved through Netease cloud search, then added to a new 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": {
      "songs_json": "<songs_json>"
    },
    "name": "create_ncm_playlist"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No
`count`	No
`prompt`	No
`avoid_days`	No
`songs_json`	Yes
`playlist_name`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 9, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and discloses the two-step behavior: songs are resolved via Netease cloud search and then added to a newly created playlist. It omits auth/cookie prerequisites, what happens when a song cannot be resolved, and playlist visibility, so meaningful gaps remain for a mutation tool.

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?

Two short sentences, front-loaded with the purpose and followed by the mechanism, with no filler. Minor waste in the redundant "real" and the reliance on a sibling reference in place of a direct statement.

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?

For a 6-parameter creation tool with zero schema description coverage and no annotations, the description does too little: no parameter meaning, no prerequisites, no failure behavior. An output schema exists so return values need no explanation, but the input side is effectively undocumented.

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% across 6 parameters (date, count, prompt, avoid_days, songs_json, playlist_name), and the description explains none of them. The cross-reference "same arguments and same contract as create_qq_playlist" only helps an agent that already knows that tool's semantics and is not self-contained.

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 concrete verb and resource ("Create a real Netease Cloud Music playlist") and ties it to a specific platform, which distinguishes it from create_qq_playlist and create_kugou_playlist. The word "real" is unexplained and the purpose statement would be cleaner without it.

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?

No explicit when-to-use or when-not-to-use guidance; the only routing signal is the platform name and the note that arguments match create_qq_playlist. Nothing tells an agent when to pick this over create_daily_playlist or add_songs_to_playlist.

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