rekordbox-mcp

by Galb-collab

Overview Schema Source Related Servers Discussions Admin

Python

Local

add_tracks_to_playlist

Idempotent

Add multiple tracks to an existing rekordbox playlist in a single operation, directly updating your database.

Instructions

Add multiple tracks to an existing playlist in one operation.

⚠️ CAUTION: This modifies your rekordbox database!

Args: playlist_id: ID of the playlist to modify track_ids: List of track IDs to add

Returns: Detailed results of the batch operation

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": {
      "playlist_id": "<playlist_id>",
      "track_ids": "<track_ids>"
    },
    "name": "add_tracks_to_playlist"
  }
}

Input Schema

Name	Required	Description	Default
`track_ids`	Yes
`playlist_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond annotations (readOnlyHint=false, idempotentHint=true), the description adds a strong caution 'This modifies your rekordbox database!' and notes it returns 'Detailed results.' This provides extra context about the mutation and outcome, going beyond the structured hints.

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 compact and well-structured: a clear purpose sentence, a warning, a concise Args list, and a Returns statement. Every element earns its place without redundancy.

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?

Given the tool's moderate complexity, the description covers purpose, parameters, return results, and a safety caution. With annotations and an output schema present, it is sufficiently complete for typical use, though it omits edge-case behaviors like duplicate handling or error cases.

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 has 0% description coverage, but the description defines both parameters: playlist_id as 'ID of the playlist to modify' and track_ids as 'List of track IDs to add.' This meaningfully explains each parameter's role, compensating for the schema's lack of detail.

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 clearly states 'Add multiple tracks to an existing playlist in one operation,' specifying the verb, resource, and batch scope. This distinguishes it from the sibling 'add_track_to_playlist' by emphasizing multiplicity and single-operation behavior.

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?

The phrase 'in one operation' implies batch use, and 'existing playlist' sets context, but no alternate tool is mentioned or explicit when-to-use vs. when-not-to-use guidance is provided. Usage is implied rather than clearly specified.

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