lms-mcp

save_playlist

Save the current playlist from a specific player to a named playlist in your music library.

Instructions

Save the current player playlist as a named 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": {
      "playerId": "<playerId>",
      "name": "<name>"
    },
    "name": "save_playlist"
  }
}

Input Schema

Name	Required	Description	Default
`playerId`	Yes	Player ID whose current playlist to save
`name`	Yes	Name for the saved playlist

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 23, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already indicate non-read-only. Description adds that it saves the 'current' playlist, but does not disclose potential overwriting behavior, permission needs, or side effects beyond the mutation implied by 'save'.

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?

Single sentence, front-loaded with key information, no unnecessary words. Perfectly concise for the tool's simplicity.

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 simplicity (2 required params, no output schema, no enums), the description covers the essential purpose. Could potentially mention if saving with an existing name overwrites or errors, but not critical.

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 100% with clear parameter descriptions. The tool description does not add any additional meaning beyond what the schema provides, so baseline score applies.

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?

Clearly states verb 'save', resource 'current player playlist', and outcome 'as a named playlist'. Distinguishes it from sibling tools like delete_saved_playlist and rename_saved_playlist.

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?

Implies usage context (saving current playlist) but provides no explicit guidance on when to use this tool versus alternatives like add_to_playlist or clear_playlist. No exclusion criteria mentioned.

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