Skip to main content
Glama
ni-c

audiobookshelf-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete media progress

delete_media_progress
DestructiveIdempotent

Remove a user's listening history for an item by deleting its progress record. Requires the media progress ID, and a confirmation token when prompted.

Instructions

Deletes a progress record of the API key’s user, which removes the listening history for that item — position, finished state and dates. Takes the media progress id (field "id" of get_media_progress), not the library item id. 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
confirm_tokenNoToken from the first call of this tool
media_progress_idYesMedia progress id, from the "id" field of get_media_progress

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
truncatedNoPresent only when the answer was shortened to fit the budget.
deleted_progress_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 / media_progress_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_progress_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_progress_id"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already indicate destructive and idempotent behavior, but the description adds specific details: it removes listening history including position, finished state, and dates, and discloses the confirmation token mechanism. This goes beyond what annotations provide.

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?

Three sentences, each with a distinct purpose: what it does, id clarification, and confirmation process. No redundancy, well-structured and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the destructive nature and the two-step confirmation, the description covers the essential behavioral requirements. The output schema exists (not shown) so return values are likely documented. No critical information missing.

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 descriptions cover both parameters, but the description adds semantic clarification: the media_progress_id is specifically the 'id' from get_media_progress, not the library item id, and confirms the confirm_token flow. This adds value over the schema alone.

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 (deletes a progress record) and the resource (media progress of the API key's user), and specifies what is removed (position, finished state, dates). It distinguishes from get_media_progress by clarifying the id source, making the purpose unambiguous.

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

Usage Guidelines4/5

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

It provides explicit guidance on which id to use (the 'id' field of get_media_progress, not the library item id) and explains the two-step confirmation flow, which is essential for correct invocation. It does not explicitly state when not to use it, but the context implies it's for removal of progress.

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