Skip to main content
Glama
ni-c

audiobookshelf-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete playlist

delete_playlist
DestructiveIdempotent

Delete a playlist while keeping its media in the library. Call once to receive a confirmation token, then call again with the token to complete deletion.

Instructions

Deletes a playlist. The media stays in the library. Asks a person first; where the client cannot show a dialog, call once to receive a token and again with it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
playlist_idYesPlaylist id, as returned by list_playlists
confirm_tokenNoToken from the first call of this tool

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
truncatedNoPresent only when the answer was shortened to fit the budget.
deleted_playlist_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / confirm_token / maxLength
      Added value: +128
    • addedInput schema / properties / playlist_id / maxLength
      Added value: +128
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "properties": {
+    "deleted_playlist_id": {
+      "type": "string"
+    },
+    "truncated": {
+      "additionalProperties": false,
+      "description": "Present only when the answer was shortened to fit the budget.",
+      "properties": {
+        "dropped_entries": {
+          "additionalProperties": {
+            "type": "number"
+          },
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "follow_up": {
+          "type": "string"
+        },
+        "reason": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "reason",
+        "dropped_entries",
+        "follow_up"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "deleted_playlist_id"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.1

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses the key behavioral nuance: that deletion is not immediate and requires a confirmation token. It also states that media items are not deleted, which is a critical side-effect not inferable from the tool name alone. This fully informs the agent of the tool's behavior.

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 concise, using just three short sentences to convey the action, the non-destructive nature to media, and the confirmation requirement. It is well-structured, front-loading the core purpose and then adding necessary context without redundancy.

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?

The description covers the essential context: what is deleted, what is not deleted, and the confirmation flow. Since the output schema exists, return values need no explanation. It omits potential error cases or permission requirements, but for a tool of this simplicity, the provided context is sufficient for correct invocation.

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?

Schema coverage is 100%, so the baseline is 3. The parameter descriptions add meaningful context: playlist_id is tied to the output of list_playlists, and confirm_token is explained as coming from the first call. This makes the flow clear, but confirm_token's optionality or requiredness in the second call could be more explicit, though the description covers it implicitly.

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 tool's primary action—'Deletes a playlist'—and distinguishes it from related operations by adding 'The media stays in the library,' which clarifies it does not delete underlying items. This makes it easily distinguishable from sibling tools like create_playlist, update_playlist, or add_items_to_playlist.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance for the confirmation flow: 'Asks a person first; where the client cannot show a dialog, call once to receive a token and again with it.' This tells the agent exactly when and how to handle the two-step deletion process, covering both dialog-capable and non-dialog environments.

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