Skip to main content
Glama
Sign In
rekordbox-mcp

rekordbox-mcp

by Galb-collab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_playlist_tracks

Retrieve all tracks in a specific playlist by providing its playlist ID. Returns a complete list of tracks for that playlist.

Instructions

Get all tracks in a specific playlist.

Args: playlist_id: The unique playlist identifier

Returns: List of tracks in the 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": {
      "playlist_id": "<playlist_id>"
    },
    "name": "get_playlist_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
playlist_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the return type (list of tracks) but does not mention error handling, ordering, or whether the operation is read-only (which is implied by 'Get'). This is adequate but not rich.

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 brief, front-loaded, and contains only necessary information: the purpose, the argument, and the return value. No fluff or 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?

For a simple getter with one parameter and an output schema, the description is sufficient. It covers what the tool does and the main input/output. Additional details like error cases or edge conditions would be nice but are not essential for this tool's complexity.

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

Parameters3/5

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

Schema coverage is 0%, but the description provides a basic argument description ('The unique playlist identifier'). This adds only minimal clarity beyond the schema, which already indicates the parameter name and type. No guidance on obtaining the ID or format is provided.

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 the tool gets all tracks in a specific playlist, which is a specific verb+resource combination. This distinguishes it from sibling tools like get_playlists (returns playlists) or search_tracks (searches across all tracks).

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?

The description implies when to use it: whenever you need the tracks of a known playlist. No explicit alternatives or exclusions are given, but the context is clear and simple.

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

Deploy Server

Other Tools