crates-music-mcp

Overview Schema Source Related Servers Discussions Admin

create_qq_playlist

Creates a real QQ Music playlist from a songs JSON list, with optional naming, song count, date, and recent-song deduplication controls to build playlists that match user requests.

Instructions

Create a real QQ Music playlist.

songs_json: {"playlist_name":"清晨慢摇","songs":[{"name":"歌名","artist":"歌手"}]} count: how many songs to add (default 20) playlist_name: explicit name from the user; leave empty to auto-name date: YYYYMMDD (default today) prompt: original user request, used to decide the name avoid_days: skip songs recommended in the last N days (default 7; 0 = no dedup) Returns {"ok","playlist_name","playlist_id","added","failed","reused_recent", "name_source"}. The name has NO date prefix here (only create_daily_playlist adds one), and it is capped at 20 characters.

If the result has need_login=true, this platform is not logged in yet: show the methods list to the user, let them pick ONE, then retry.

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_qq_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

A4.2/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 well: it lists the exact return keys, discloses the 20-character name cap, explains that auto-naming happens when playlist_name is empty, documents the avoid_days dedup window, and gives a concrete remediation path for need_login=true. It does not address whether repeated creates produce duplicate playlists or what a false ok means.

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?

Front-loaded with a one-line purpose, then a scannable parameter block, a return-key list, and two caveats. Dense but every line carries information; the run-together formatting of the parameter block slightly reduces readability.

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 six-parameter creation tool with no annotations, the definition covers inputs, outputs, naming behavior, and login failure handling. An output schema exists, so the return-key list is somewhat redundant, but the ambiguity around count versus songs_json is the remaining gap.

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

Parameters5/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 supply everything and it does: every one of the six parameters gets format or default detail, including a concrete songs_json shape and the YYYYMMDD date format. The one soft spot is whether count overrides the length of the songs array in songs_json, which is left ambiguous.

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 ("Create a real QQ Music playlist") and the platform qualifier separates it from create_kugou_playlist and create_ncm_playlist. The explicit note that only create_daily_playlist adds a date prefix further distinguishes it from the closest sibling.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the date-prefix note tells the agent this is the non-daily variant, and the need_login retry procedure gives operational guidance. There is no explicit statement of when to pick this over create_daily_playlist or add_songs_to_playlist, so the agent must infer the routing.

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