Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete watch progress

nuvio_delete_watch_progress
Destructive

Delete specific continue-watching entries using content ID and optional season/episode. Use dry-run to preview changes before confirming the removal.

Instructions

Delete continue-watching entries using structured keys (content_id + optional season/episode). Supports dry_run and snapshots the previous state before the write; revert with nuvio_undo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keysYes
confirmNoRequired to actually apply a destructive change. Without it a preview is returned.
dry_runNoReturn the diff without writing anything (no snapshot, no audit entry).
profile_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.1.1
    • changedInput schema / properties / confirm / description
      Previous value: -"Required for reversible destructive changes. Without it a preview is returned."New value: +"Required to actually apply a destructive change. Without it a preview is returned."
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Return the diff without writing anything (no snapshot, no audit entry).",
+  "type": "boolean"
+}
    • removedInput schema / properties / keys / description
      Removed value: -"Progress keys"
    • addedInput schema / properties / keys / items / properties
      Added value: +{
+  "content_id": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "episode": {
+    "anyOf": [
+      {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "season": {
+    "anyOf": [
+      {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  }
+}
    • addedInput schema / properties / keys / items / required
      Added value: +[
+  "content_id"
+]
    • changedInput schema / properties / keys / items / type
      Previous value: -"string"New value: +"object"
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, and the description adds valuable behavior beyond that: it supports dry_run and snapshots the previous state before the write, with revert via nuvio_undo. This gives the agent useful operational context not present in the annotation or schema.

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 two sentences with zero filler: the action and key structure are front-loaded, followed by the dry_run and snapshot/undo behavior. Every clause earns its place.

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 destructive tool with a moderately complex keys parameter, the description covers the core semantics, key structure, dry-run behavior, and undo path. It omits explicit mention of the confirm parameter, but the schema already documents that, so the description is largely complete.

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?

With schema description coverage at 50%, the description compensates by explaining the keys parameter structure (content_id plus optional season/episode), which is the most complex parameter. It does not elaborate on profile_id, but that parameter has a simple default and range in the schema.

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 states a specific action (delete) on a specific resource (continue-watching entries) and defines the key structure (content_id + optional season/episode). This clearly distinguishes it from siblings like nuvio_delete_watch_history, which targets history rather than progress.

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?

The description does not explicitly state when to use this tool vs alternatives such as nuvio_delete_watch_history or nuvio_set_watch_progress. It implies usage through the action and key structure, and mentions dry_run and undo, but provides no when-not-to-use guidance or direct sibling routing.

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