Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update a collection folder

nuvio_update_collection_folder

Update a collection folder's title, cover, tile shape, or catalog sources. Preview changes with a dry run; previous state is snapshotted before writing for undo support.

Instructions

Edit a folder's title, cover, tile shape or catalog sources. Supports dry_run and snapshots the previous state before the write; revert with nuvio_undo.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.1
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Return the diff without writing anything (no snapshot, no audit entry).",
+  "type": "boolean"
+}
  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 the annotations, the description reveals that the write snapshots the previous state, supports dry_run, and can be reverted with nuvio_undo. This materially informs an agent about safety, side effects, and recovery options.

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 terse sentences: the first states the core edit scope and the second covers dry-run and snapshot/revert behavior. There is no filler, and the most important information is 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?

The description plus schema gives an agent enough to make a typical call: what fields can be edited, a dry-run escape hatch, and snapshot/undo safety. However, given the nested changes object and no output schema, a bit more detail on update semantics, such as partial merge versus full replacement for catalogSources, would make it fully complete.

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?

Schema description coverage is only 20%, so the description must compensate. It maps the changes object to high-level concepts like title, cover, tile shape, and catalog sources, and mentions dry_run, but it does not clarify the semantics of collection_id, folder_id, profile_id, or whether catalogSources merges or replaces existing sources.

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 opens with 'Edit a folder's title, cover, tile shape or catalog sources', which names a specific verb, resource, and the editable fields. It also clearly distinguishes this tool from siblings like nuvio_add_collection_folder, nuvio_remove_collection_folder, and nuvio_reorder_collection_folders.

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 states the intended operation and enumerates the editable aspects, so an agent knows this is the tool for modifying an existing folder's display and source configuration. It does not explicitly name alternatives or exclusions, but the 'Edit a folder' framing and sibling names make the context clear.

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