Skip to main content
Glama

playlist_save

Save the current playlist to an .m3u, .m3u8, or .pls file to export and reuse it in compatible media players.

Instructions

Save the current playlist to an .m3u, .m3u8, or .pls file.

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": {
      "path": "<path>"
    },
    "name": "playlist_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesDestination file path (.m3u, .m3u8, or .pls)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 behavioral burden, and it discloses only that a file is written at the given path. It says nothing about whether an existing file is overwritten, whether the parent directory must exist, what happens with an empty playlist, or what errors the caller should expect from a write operation.

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?

One front-loaded sentence that states the action, the object, and the accepted formats with zero filler. Nothing could be removed without losing information.

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?

The tool is simple (one required parameter, no nested objects, no output schema), so the description is close to adequate. However, for an unannotated file-writing tool, the absence of any overwrite/error behavior leaves a real gap for an agent deciding whether calling it is safe.

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 the single `path` parameter is already documented with the same three extensions in the schema. The description adds no format-selection semantics (e.g. extension determines format, or whether an extension is auto-appended), so it merely mirrors structured data.

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 ("Save") with a specific resource ("the current playlist") and names the supported output formats, so the agent knows this persists the in-memory playlist to disk. It implicitly contrasts with playlist_load, but never names it or any other sibling explicitly.

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: the agent must infer that this is the tool to call when it wants to persist the current playlist rather than load, clear, or edit it. There is no explicit when-to-use guidance, no prerequisites (e.g. a non-empty playlist), and no mention of alternatives such as playlist_load for the reverse direction.

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