Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Mark as watched

nuvio_mark_watched

Add a movie or episode to a profile's watch history with dry-run and snapshot-revert support. Deprecated; use add_to_watch_history.

Instructions

[DEPRECATED] Use nuvio_add_to_watch_history instead. Add an entry to a profile's watch history. Supports dry_run and snapshots the previous state before the write; revert with nuvio_undo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemYes
dry_runNoReturn the diff without writing anything (no snapshot, no audit entry).
profile_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.1
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Return the diff without writing anything (no snapshot, no audit entry).",
+  "type": "boolean"
+}
    • addedInput schema / properties / item / properties / content_id / minLength
      Added value: +1
    • addedInput schema / properties / item / properties / content_type / minLength
      Added value: +1
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond annotations (which only indicate mutation and non-destructiveness), the description discloses that it supports dry_run, snapshots prior state before writing, and can be reverted with nuvio_undo. This adds valuable behavioral context that the annotations do not cover.

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 and packs deprecation warning, replacement, primary function, dry_run support, snapshot behavior, and revert mechanism without wasted words. Information is front-loaded and concise.

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 deprecated tool, the description adequately redirects to the alternative and explains key behaviors (snapshot, dry_run, revert). It lacks parameter details and error handling, but given the deprecation, the main purpose is to prevent misuse, which it achieves. A fully complete spec is unnecessary for a tool that should not be used.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% (only dry_run has a description). The description mentions dry_run but adds nothing beyond what the schema already states. It provides no explanation for the 'item' object (required fields, meaning of season/episode/watched_at) or 'profile_id'. Since schema coverage is low, the description should compensate but does not.

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 adds an entry to a profile's watch history, names the replacement (nuvio_add_to_watch_history), and signals deprecation. It distinguishes itself from siblings by explicitly saying to use the alternative.

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 explicitly instructs the agent to use nuvio_add_to_watch_history instead and mentions nuvio_undo for revert, providing clear when-to-use and when-not-to-use guidance. This leaves no ambiguity.

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