Skip to main content
Glama

playlist_play

Play a specific playlist entry by index to start the selected item in Unflick's media player.

Instructions

Play a specific playlist entry 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": {
      "index": "<index>"
    },
    "name": "playlist_play"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYesIndex of the playlist entry to play

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it discloses little: nothing about whether playback starts immediately or queues, whether it requires an active playlist, what happens on an out-of-range index, or whether the index is zero- or one-based. These are exactly the details an agent needs to avoid a failed call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no filler and the key qualifier ('by index') placed where it matters. It is efficient, though so terse that the remaining useful context was left out rather than trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter playback tool with no output schema and no annotations, the bar is low and the purpose is conveyed. Still, prerequisites (loaded playlist) and index conventions are missing, leaving an agent able to guess the call but not guaranteed to make it correctly.

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% and there is only one integer parameter, so the schema already documents the parameter adequately; baseline 3 applies. The description adds no meaning beyond the schema — notably it does not clarify index origin or valid bounds.

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?

The description pairs a specific verb ('Play') with a specific resource ('a specific playlist entry') and a selection mechanism ('by index'), which distinguishes it from playlist_next/playlist_prev. It does not explicitly name or contrast with the plain 'play' sibling, so an agent must still infer whether 'play' also targets playlist entries.

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 phrase 'specific playlist entry by index' implies usage when the caller already knows the target position, versus stepping sequentially with playlist_next/playlist_prev, but no explicit when-to-use or when-not guidance is given. Nothing states whether a playlist must first be loaded via playlist_load.

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