rekordbox-mcp

Overview Schema Source Related Servers Discussions Admin

create_playlist

Create a new playlist or folder in your rekordbox library, optionally nested within an existing folder. Use this to structure your tracks for DJ sets.

Instructions

Create a new playlist or folder in rekordbox.

⚠️ CAUTION: This modifies your rekordbox database!

Args: name: Name for the new playlist or folder parent_id: Optional parent folder ID (omit for root level) is_folder: If True, create as a folder that can contain other playlists

Returns: Information about the created playlist or folder

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": {
      "name": "<name>"
    },
    "name": "create_playlist"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`is_folder`	No
`parent_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description adds a caution about modifying the rekordbox database, which goes beyond the annotations. It also mentions the return information. It does not contradict annotations.

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

Conciseness5/5

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

The description is concise and well-structured with a clear warning, parameter list, and return statement. Every sentence adds value.

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 create tool with three parameters and an output schema, the description covers purpose, parameters, and return. It doesn't mention edge cases or prerequisites, but it's sufficiently complete for selection and invocation.

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?

The Args section explains each parameter (name, parent_id, is_folder) with semantics not present in the input schema, which has no descriptions. Since schema coverage is 0%, the description fully compensates.

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?

The description states a specific action ('Create a new playlist or folder in rekordbox'), clearly distinguishing it from sibling tools like delete_playlist or add_tracks_to_playlist. The verb and resource are explicit.

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

Usage Guidelines4/5

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

It provides clear context for when this tool is appropriate (creating a playlist or folder) but doesn't explicitly exclude or reference alternatives like add_tracks_to_playlist. No prerequisites are required, making the usage context clear.

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