Skip to main content
Glama
Sign In
mia

mia

by akadorkin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

jellyfin_library_create

Create a Jellyfin library from specified folders, optionally copying metadata and fetcher options from an existing library or using Jellyfin defaults.

Instructions

Create a Jellyfin library with folders. Library options (metadata language, savers, fetchers …) can be copied from an existing library of your choice; otherwise Jellyfin defaults apply.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "host": "<host>",
      "name": "<name>",
      "type": "<type>",
      "paths": "<paths>"
    },
    "name": "jellyfin_library_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYeshost name from the inventory that has apps.jellyfin / apps.tdarr
nameYes
scanNo
typeYes
applyNofalse (default) = dry run: show what will happen on which hosts and a planHash. true = run it; needs planHash
pathsYesfolders (host or container paths)
planHashNoplanHash from the dry run of the very same call, good for one apply; refused if targets or their state changed since
optionsFromNoexisting library whose LibraryOptions to copy

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and discloses only that library options may be copied or defaulted. It says nothing about the mutation's side effects, the fact that apply defaults to a dry run requiring a one-shot planHash, permissions, or irreversibility — all of which matter for a create operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly written sentences with the core action front-loaded and the options nuance trailing; no filler. Slight verbosity with the parenthetical '…' ellipsis list, but otherwise efficient.

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

Completeness2/5

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

For an 8-parameter mutation tool with no annotations, no output schema, and 63% schema coverage, the description omits the most consequential facts: the dry-run-first/apply contract, that optionsFrom is the sole options source, and scan defaults. An agent could invoke it without realizing the default call is a no-op dry run.

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 coverage is 63%, so the schema already documents several parameters (host, apply, paths, planHash). The description's only parameter-level contribution is restating optionsFrom ('copy from an existing library of your choice') plus 'with folders' for paths, adding little beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a Jellyfin library with folders'), which is enough to distinguish it from jellyfin_library_add_path (adds a path to an existing library) and jellyfin_scan. It does not explicitly name those siblings, but the verb+resource is unambiguous.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus jellyfin_library_add_path, nor any mention of the dry-run/apply workflow that governs safe invocation. The only conditional offered is the internal optionsFrom behavior, not guidance about tool selection.

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