Skip to main content
Glama

kavita_series

Destructive

Query and manage Kavita series by retrieving metadata, volumes, chapters, relations, and reading status, or executing confirmed scan, match, update, and delete operations.

Instructions

kavita_series covers the series toolset (33 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_age_rating, get_all_related, get_chapter, get_currently_reading, get_external_series_detail, get_match_info, get_metadata, get_next_expected, get_related, get_series_by_collection, get_series_detail, get_series_with_annotations, get_volume, get_volumes, post_all_v2, post_analyze, post_delete_multiple, post_dont_match, post_match, post_metadata, post_on_deck, post_recently_added_v2, post_recently_updated_series, post_refresh_metadata, post_remove_from_on_deck, post_scan, post_series_by_ids, post_update, post_update_match, post_update_related, post_v2.

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

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

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description goes notably beyond them: it documents the confirm-gating contract, that omitting confirm sends nothing at all, that writes additionally require KAVITA_ALLOW_WRITES=true, and that an extra warning is emitted for delete/scan/analyze/refresh/cache/cleanup/user/role/auth-key/password/settings/license/scrobbling/OAuth/email actions. That is genuinely useful side-effect disclosure for a destructive tool. Not covered: partial-failure behavior, whether any action is idempotent, or whether the dry-run preview reports the exact request that would be sent.

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?

The behavioral contract is front-loaded well: purpose first, then auth, then help, then write gating, then the destructive list. However, the trailing enumeration of all 33 action names duplicates the action enum already present in the input schema, consuming roughly a third of the text without adding information. Trimming that list, or grouping actions into read versus write versus destructive buckets, would make the definition tighter and more scannable.

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 33-operation mega-tool with no output schema, the description supplies the essentials an agent needs to act safely: auth mechanism, self-hosted constraint, write confirmation protocol, dry-run preview, and an escalation list for dangerous actions, plus a pointer to the help action for per-action parameters. The remaining gap is that it never explains what any individual action returns or requires, relying entirely on the help escape hatch and the OpenAPI-derived schema.

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 100%, so action, body, query, params, target and confirm are all already documented in the schema, and the description largely restates the confirm/dry-run and help-target semantics rather than extending them. It does add the cross-cutting fact that bodies are per-action Kavita payloads and that secrets are redacted, but it gives no per-action guidance on which params/query/body fields each of the 33 operations expects. Baseline 3 is appropriate given the schema does the heavy lifting.

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 first sentence pins down the resource ('kavita_series covers the series toolset') and enumerates the concrete operations, and the action names (get_series_detail, post_scan, post_match, get_volumes) make the series-scoped domain obvious against siblings like kavita_chapter and kavita_library. It is clear what resource family this tool operates on, but the individual 33 actions are listed only by name with no gloss, so an agent still needs the help action to tell what most of them do.

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 gives real routing guidance: 'action help with target returns one action's parameters', omit confirm for a dry-run preview, and set confirm true to execute. The auth prerequisites (x-api-key header or JWT from KAVITA_USERNAME/KAVITA_PASSWORD, KAVITA_ALLOW_WRITES=true) and the 'Self-hosted Kavita only' constraint define when this tool is usable. What is missing is any explicit statement of when to pick kavita_series over a sibling such as kavita_metadata for metadata reads or kavita_volume for volume details.

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