Skip to main content
Glama

kavita_collection

Destructive

Manage Kavita collections by retrieving, importing, promoting, updating, and deleting collection entries, with dry-run previews and explicit confirmation required for write operations.

Instructions

kavita_collection covers the collection toolset (12 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, get, get_all_series, get_mal_stacks, get_name_exists, get_single, post_delete_multiple, post_import_stack, post_promote_multiple, post_update, post_update_for_series, post_update_series.

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_collection"
  }
}

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/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds substantial context beyond them: the auth mechanism (x-api-key or JWT from env credentials), the write gate requiring both confirm=true and KAVITA_ALLOW_WRITES=true, the dry-run preview that sends nothing, and an explicit enumeration of which actions trigger extra destructive warnings. That is exactly the behavioral detail an agent needs before invoking a mutating dispatcher.

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?

Scope is front-loaded, followed by auth, write gating, and the action list — a logical order with no filler sentences. The long destructive-action enumeration is dense but earns its place by warning about credential and exposure operations.

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 12-operation, 6-parameter dispatcher with nested objects and no output schema, the description covers auth, write safety, dry-run behavior, help-based discovery, and the destructive set. It stops short of describing per-action behavior or response shape, though the help action partially compensates for the former.

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 the baseline is 3, but the description adds meaning the schema does not fully carry: the help+target pattern for parameter discovery and the fact that the dry-run preview sends nothing to the server. The confirm semantics are largely duplicated from the schema, which keeps it from a 5.

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?

The description names the resource domain ('kavita_collection covers the collection toolset') and enumerates all 12 actions, so an agent knows this is the collection dispatcher rather than library/series/person tooling. It does not explicitly contrast with siblings like kavita_series, whose action names (get_all_series, get_single) overlap conceptually, leaving a small ambiguity.

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?

It gives real procedural guidance: use 'action help with target' to discover an action's parameters, set confirm=true for writes, omit confirm for a dry-run, and self-hosted Kavita only. What it lacks is explicit routing guidance against the 11 sibling tools — an agent must infer that collection operations belong here and series operations belong in kavita_series.

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