Skip to main content
Glama

playlist_add

Adds a media file from a specified path to the current playlist so you can queue it for playback.

Instructions

Add a file to the 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": {
      "file": "<file>"
    },
    "name": "playlist_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesPath to the media file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden for a mutation. It says nothing about whether the file is appended or inserted, whether duplicates are allowed, whether missing files error out, or if the change is persisted or only affects the current session.

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 wasted wording, front-loading the verb and resource. It is efficient, though the brevity leaves no room for the operational context an agent would need.

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 tool with no output schema, the definition covers the minimum needed to call it. However, with zero annotations and no output schema, the description should at least state whether a playlist must already be loaded and what happens on failure, which it omits.

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% and the single 'file' parameter is documented as a path to the media file, so the schema already does the heavy lifting. The description adds no format, path-resolution, or validation detail beyond that.

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?

"Add a file to the playlist" names a specific verb (add) and resource (playlist entry), so the agent knows exactly what operation it performs. It falls short of a 5 because nothing distinguishes it from siblings that also populate a playlist, such as playlist_load, leaving the agent to infer the difference from name alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites (e.g. must a playlist exist first?), and no reference to sibling alternatives like playlist_load or playlist_remove. The agent must guess the context in which adding is the right action.

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