vlc-mcp

Overview Schema Source Related Servers Discussions Admin

get_playlist

Lists VLC playlist items with their IDs and marks the currently playing item, so you can identify and select a specific track.

Instructions

List the items in the VLC playlist with their ids. The current item is marked with *.

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": "get_playlist"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden; it does partially deliver by disclosing the output convention that the current item is marked with *. It says nothing about ordering, behavior on an empty playlist, or whether the call has side effects, which for an unannotated tool is a meaningful gap.

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 short sentences, front-loaded with the action and followed by the notable output convention. Nothing is padded or redundant.

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 zero-parameter read tool with an output schema available, the description covers what is needed to select and call it. Only playback ordering and empty-list behavior are left unstated, and both are minor.

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?

Zero parameters, so there is no parameter meaning to add; the baseline applies. The description correctly adds no noise about inputs.

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?

A specific verb ("List") plus resource ("items in the VLC playlist") and it says what fields come back (ids, current-item marker). It does not name any sibling to distinguish itself from, but the read-only listing scope is unmistakable against siblings like play_playlist_item or remove_playlist_item.

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 only implied: an agent can infer you call this to inspect the playlist before acting on it. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative (e.g., use get_status for playback state instead).

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