Skip to main content
Glama

playlist-set

Create a playlist (no playlistId; name required) or change one, and add, import or change its sounds in the same call. importPaths adds files named after themselves; find paths with file-list. Removing: playlist-delete. Requires bridge module 8.19.0+.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "playlist-set"
  }
}

Input Schema

NameRequiredDescriptionDefault
fadeNoCrossfade, ms
modeNoPlayback mode
nameNo
channelNoVolume channel
folderIdNoFolder ID (from folder-list); null = root
addSoundsNoSounds to add: [{name, path, volume?, repeat?}]
playlistIdNoPlaylist ID (from playlist-list); omit to create
descriptionNo
importPathsNo1–100 audio file paths to add
updateSoundsNoSound changes: [{soundId, name?, path?, volume?, repeat?}]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, openWorld=false, so the safety profile is covered; the description adds real context beyond that — the bridge module 8.19.0+ version requirement and the fact that importPaths names added files after themselves. It stops short of saying how the tool behaves if addSounds, updateSounds and importPaths are supplied together, or whether failures are atomic.

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?

Three tight sentences, front-loaded with the primary capability, then import mechanics, then the removal alternative and version gate. Parentheticals carry density without padding, and nothing is repeated from the schema.

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 10-parameter create-or-update tool with no output schema, the description covers the create/update distinction, imports, the delete sibling and the runtime requirement. The remaining gap is how the three sound-mutating arrays interact and what the call returns, which would help an agent compose a complex invocation.

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 80%, so the baseline is 3; the description earns an extra point by explaining the playlistId-omitted create semantics and the required name, which the schema does not express as conditional requirements, plus the naming behavior of importPaths. It does not clarify the relationship between addSounds, updateSounds and importPaths beyond their individual roles.

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+resource ('Create a playlist ... or change one') and enumerates the sub-operations (add, import, change sounds) in the same call. The parenthetical 'no playlistId; name required' immediately distinguishes create-mode from update-mode, which no sibling name alone would convey.

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

Usage Guidelines5/5

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

Explicitly routes the agent: omit playlistId to create, and 'Removing: playlist-delete' names the alternative for the delete case. It also points to file-list for obtaining import paths, so the prerequisite chain is stated rather than inferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources