Skip to main content
Glama

playlist_load

Loads .m3u, .m3u8, or .pls playlist files into the player queue, resolving relative paths from the playlist directory; append to or replace the current queue.

Instructions

Load an .m3u, .m3u8, or .pls playlist file into the player's queue. Relative paths inside the playlist are resolved against the playlist file's directory.

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

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the .m3u, .m3u8, or .pls playlist file
appendNoAppend to the existing playlist instead of replacing it (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It helpfully discloses that relative paths inside the playlist are resolved against the playlist directory, but it never states the critical default behavior that loading replaces the current queue (only inferable from the schema's append=false), nor how missing/duplicate entries or malformed files are handled.

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?

Two sentences, zero filler, with the core action front-loaded before the path-resolution detail. Every sentence adds information that is not available from the tool name alone.

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 two-parameter, low-complexity tool with no output schema, this is close to sufficient, and the path-resolution note is genuinely useful. The remaining gaps are the default queue-replacement behavior and what happens on invalid paths or whether anything is returned.

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 coverage is 100%, so the baseline is 3; the description earns an extra point by explaining the path-resolution semantics for `path`, which the schema does not. It does not otherwise elaborate on `append`, leaving that to the schema.

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 specific verb ('Load') plus the exact resource types (.m3u, .m3u8, .pls) and destination ('the player's queue'), which distinguishes it from playlist_add and playlist_save by resource shape. It stops short of naming a sibling or contrasting it explicitly, so it is not a clean 5.

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 clearly by the file-type scoping and the 'queue' target, but there is no explicit when-to-use or when-not statement and no reference to alternatives such as playlist_add (add individual entries) or playlist_clear. An agent can infer the use case but must reason about the sibling distinction itself.

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