Skip to main content
Glama

kavita_metadata

Read-only

Retrieve Kavita metadata such as genres, tags, languages, people, publication status, series details, and counts for library cataloging and filtering.

Instructions

kavita_metadata covers the metadata toolset (14 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. Actions: get_age_ratings, get_all_bcp47_languages, get_all_languages, get_genres, get_language_title, get_languages, get_people, get_people_by_role, get_publication_status, get_readinglist_tags, get_series_detail_plus, get_tags, post_genres_with_counts, post_tags_with_counts.

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

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, yet the description adds real behavioral context: auth via x-api-key header or JWT from KAVITA_USERNAME/KAVITA_PASSWORD, and the self-hosted-only deployment constraint. It does not clarify why post_genres_with_counts and post_tags_with_counts are POST-named actions under a readOnly hint, which is exactly the ambiguity an agent would need resolved.

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, then auth, then the help mechanism, then the action inventory — a sensible ordering with no filler. The action list is long but each entry is a single token and the list is the tool's essential payload.

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

Completeness3/5

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

For a 14-action dispatcher with only generic body/query/params containers and no output schema, the description never says what any individual action returns or requires beyond its name. The help escape hatch partially compensates, but an agent must make a discovery call before it can use most actions correctly.

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 body, query, params, action and target are already documented. The description still adds meaning by telling the agent that the target parameter, combined with action=help, is the mechanism for discovering per-action parameters that the generic body/query/params objects cannot express. That is a genuine step 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?

The description names the resource (Kavita metadata toolset) and enumerates all 14 actions, so an agent can see the scope without opening the schema. It also implicitly separates itself from siblings like kavita_series or kavita_person by framing everything as metadata lookup. However, the action names alone are opaque (e.g. get_series_detail_plus, post_tags_with_counts) and the boundary with kavita_series or kavita_person is never stated.

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 one concrete usage rule: call action=help with target to retrieve a specific action's parameters, which is genuinely useful for navigating a 14-operation dispatcher. It offers no guidance on when to pick this tool over kavita_series or kavita_person, and no indication of which actions are safe reads versus anything else.

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