Skip to main content
Glama

playlist_delete

Delete a saved playlist by name to remove unwanted playlist files from mpv media player, keeping your library organized.

Instructions

Delete a saved playlist file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPlaylist name to delete

Implementation Reference

  • Handler for playlist_delete tool: constructs the playlist path, checks if it exists, deletes the file, and returns success or error.
    case "playlist_delete": {
      const p = playlistPath(args.name);
      if (!fs.existsSync(p)) return fail(`Playlist "${args.name}" not found`);
      fs.unlinkSync(p);
      return ok(`Deleted playlist "${args.name}"`);
    }
  • Schema definition for playlist_delete tool: requires 'name' (string) as input.
    {
      name: "playlist_delete",
      description: "Delete a saved playlist file.",
      inputSchema: {
        type: "object",
        properties: {
          name: { type: "string", description: "Playlist name to delete" },
        },
        required: ["name"],
      },
    },
  • index.js:487-498 (registration)
    Tool registration: playlist_delete is part of the TOOLS array used in ListToolsRequestSchema handler.
      {
        name: "playlist_delete",
        description: "Delete a saved playlist file.",
        inputSchema: {
          type: "object",
          properties: {
            name: { type: "string", description: "Playlist name to delete" },
          },
          required: ["name"],
        },
      },
    ];
  • Helper function that constructs the filesystem path for a playlist by sanitizing the name and appending .m3u extension.
    function playlistPath(name) {
      return path.join(PLAYLIST_DIR, name.replace(/[/\\?%*:|"<>]/g, "_") + ".m3u");
    }
Behavior2/5

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

No annotations are provided, and the description only states the action without disclosing behavioral details such as irreversibility, side effects, or required permissions. The description does not compensate for the lack of annotations.

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?

The description is a single concise sentence that directly states the tool's purpose with no unnecessary words. It is well-structured and front-loaded.

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 deletion tool with one parameter and no output schema or annotations, the description is mostly complete. It fully explains the action and parameter, though additional behavioral details would be beneficial.

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?

The input schema has 100% coverage with a simple string parameter 'name' described as 'Playlist name to delete'. The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 the action (delete) and the resource (saved playlist file). It distinguishes from sibling tools like playlist_create or playlist_list, as deletion is a distinct operation.

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?

No guidance is provided on when to use this tool versus alternatives like playlist_remove. The description does not mention prerequisites or scenarios for using this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/guodaxia9527/mcp-mpv-player'

If you have feedback or need assistance with the MCP directory API, please join our Discord server