lms-mcp

delete_playlist_item

Destructive

Delete a specific track from the current playlist by its index. Removes the unwanted song using player ID and track number.

Instructions

Delete a track from the current playlist by index

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>",
      "index": "<index>"
    },
    "name": "delete_playlist_item"
  }
}

Input Schema

Name	Required	Description	Default
`playerId`	Yes	Player ID to control
`index`	Yes	Track index to delete (0-based)

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 provide destructiveHint=true, which matches the 'Delete' action. The description adds context about 'current playlist', but does not disclose error behavior or permissions. Beyond annotations, the additional value is limited.

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 of 8 words with no filler. Perfectly sized for conveying the core action.

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 destructive tool with full schema annotations, the description is mostly complete. It lacks mention of reindexing behavior or error cases, but output schema is absent, so agent may need to infer from context. Still adequate.

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 description coverage is 100%, so baseline is 3. The description adds no extra meaning beyond 'by index', which is already in the schema. It does not elaborate on playerId.

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 'Delete a track from the current playlist by index', using a specific verb and resource. It distinguishes from siblings like clear_playlist (delete all) and delete_saved_playlist (delete playlist itself).

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 description implies usage for removing a single track by index, but does not explicitly contrast with alternatives like clear_playlist or move_playlist_item. No when-not guidance is provided.

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