Skip to main content
Glama

kavita_library

Destructive

Manage self-hosted Kavita libraries by listing, creating, updating, scanning, refreshing metadata, granting access, and deleting, with dry-run previews and explicit confirmation for writes.

Instructions

kavita_library covers the library toolset (23 operations). Auth is the x-api-key header, or a JWT from KAVITA_USERNAME and KAVITA_PASSWORD. Self-hosted Kavita only. action help with target returns one action's parameters. Writes need confirm set to the boolean true and KAVITA_ALLOW_WRITES=true. Omit confirm for a dry-run preview that sends nothing. Destructive, credential, or exposure actions add an extra warning in the preview and here: delete, scan, analyze, refresh, cache clear, cleanup, user or role changes, Auth Key create or revoke, password reset, settings, license, scrobbling tokens, OAuth or OIDC, and email. Actions: delete_delete, delete_delete_multiple, get, get_jump_bar, get_libraries, get_list, get_metadata_enabled_libraries, get_metadata_providers, get_name_exists, get_scrobble_enabled_libraries, get_type, get_user_libraries, post_copy_settings_from, post_create, post_grant_access, post_has_files_at_root, post_refresh_metadata, post_refresh_metadata_multiple, post_scan, post_scan_all, post_scan_folder, post_scan_multiple, post_update.

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": {
      "action": "<action>"
    },
    "name": "kavita_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON body for the Kavita operation. Secrets are redacted in output.
queryNoOpenAPI query parameters.
actionYesKavita operation to call, or help.
paramsNoOpenAPI path parameters, such as seriesId.
targetNoWith action help, the action whose parameters to describe.
confirmNoSet to the boolean true to execute the write. Omit this field for a dry-run preview. false and the string true are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare destructive/openWorld/non-idempotent; the description goes well beyond that with auth mechanics (x-api-key header or JWT from KAVITA_USERNAME/KAVITA_PASSWORD), the dual write gate (confirm=true plus KAVITA_ALLOW_WRITES=true), dry-run preview semantics, and an explicit list of high-risk action classes that emit extra warnings. For a destructive dispatcher this is exactly the missing operational context.

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

Conciseness3/5

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

Front-loaded and dense: auth, write gating, and warnings come before the action list, which is the right order. However, the 23-action enumeration verbatim duplicates the schema enum and consumes roughly a third of the text without adding routing information.

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 6-parameter multi-operation dispatcher with no output schema, it covers auth, write safety, dry-run behavior, and discovery via help, which is most of what an agent needs before calling. The remaining gap is per-action semantics, partially mitigated by the help/target mechanism rather than described inline.

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 coverage is 100%, so 3 is the floor; the description adds real meaning by explaining the confirm/environment-variable interaction and the dry-run default, which is not derivable from the const:true constraint alone. It also explains the help+target discovery pattern, though it says nothing extra about body, query, or params.

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 the resource explicitly ('covers the library toolset') and enumerates all 23 operations, so an agent knows this is the library-domain dispatcher among siblings like kavita_series or kavita_chapter. It never says what a Kavita library conceptually is, but the action names (get_libraries, post_scan, delete_delete) make the scope inferable.

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?

Gives concrete invocation context: 'action help with target returns one action's parameters', 'Self-hosted Kavita only', and the confirm/dry-run protocol ('Omit confirm for a dry-run preview that sends nothing'). It does not tell the agent when to prefer kavita_library over a sibling such as kavita_series, so routing between domains remains implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.