arr-mcp

Overview Schema Source Related Servers Discussions Admin

Metadata issues

get_metadata_issues

Read-only

Scan the entire media-server library for series whose metadata does not match files on disk, returning findings and suggested remedies to refresh, rename, or unlock fields.

Instructions

Sweeps the whole media-server library for series whose metadata does not describe the files on disk: the discovery fix_metadata cannot do, since it needs a title. Each row has numbering findings (confident), titleOnly findings (advisory) and a remedy: refresh_metadata, rename_files (the filename is the outlier, which no refresh fixes) or unlock_fields. Pass a row's service:itemId to fix_metadata as id. Slow: one call per series. Read-only. With Grimmory it also lists books whose match score is under 45, as grimmory:<id>. Titles and paths are fenced as untrusted data. Field reference: arr://docs/get_metadata_issues.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum items to return. Defaults to 50, hard maximum 500.
`detail`	No	How much per-item detail to return. Defaults to standard.	standard
`offset`	No	Items to skip: page two of 50 is `offset: 50`. Pair it with `sort`, or items can move between pages.

Output Schema

Name	Required	Description	Default
`items`	Yes
`total`	Yes
`counts`	No
`offset`	Yes
`degraded`	Yes
`returned`	Yes
`truncated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedv1.74.0Nov 9, 2026

removedInput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / offset / description

Previous value: -"How many items to skip before the window `limit` returns — page two of 50 is `offset: 50`. `total` always counts the whole list, so `offset + returned < total` is how you know there is another page. Pair it with `sort` for a stable walk: without one the order is whatever the services returned, and an item can move between pages."New value: +"Items to skip: page two of 50 is `offset: 50`. Pair it with `sort`, or items can move between pages."

removedInput schema / properties / offset / maximum
```
Removed value: -9007199254740991
```

removedOutput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

removedOutput schema / properties / counts / description

Removed value: -"How many results each service contributed."

removedOutput schema / properties / degraded / description

Removed value: -"Services that could not be reached. Their contribution is missing from `items`, so a short list may be an outage rather than an answer."

removedOutput schema / properties / items / description

Removed value: -"The window of results. What an item carries depends on the tool and on `detail`."

removedOutput schema / properties / offset / description

Removed value: -"How many were skipped. `offset + returned < total` means there is another page."

removedOutput schema / properties / offset / maximum
```
Removed value: -9007199254740991
```
removedOutput schema / properties / offset / minimum
```
Removed value: --9007199254740991
```
removedOutput schema / properties / returned / description
```
Removed value: -"How many are in `items`."
```
removedOutput schema / properties / returned / maximum
```
Removed value: -9007199254740991
```
removedOutput schema / properties / returned / minimum
```
Removed value: --9007199254740991
```

removedOutput schema / properties / total / description

Removed value: -"How many matched in total — the whole list, never the window. Compare against `returned` before reporting a count to anyone."

removedOutput schema / properties / total / maximum
```
Removed value: -9007199254740991
```
removedOutput schema / properties / total / minimum
```
Removed value: --9007199254740991
```

removedOutput schema / properties / truncated / description

Removed value: -"True when this is not the whole list — including on the last page of a paged walk, where the rest is behind you rather than ahead."

First observedv0.1.0Nov 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation it discloses the real cost profile (slow, one call per series), the shape of each result row (numbering vs titleOnly confidence, the three remedy values and when no refresh will help), and the untrusted-data fencing of titles and paths. It also notes the Grimmory-specific low-match-score branch, none of which is recoverable from the annotations.

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?

Front-loaded with the purpose and the sibling comparison, then behavior, then the pointer to a deeper doc. It is dense with backtick-heavy clauses and the remedy enumeration sentence takes a re-read, but almost every clause carries operational information.

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

Completeness5/5

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

For a read-only sweep with a full output schema, an agent has everything needed: cost expectations, the pagination caveat, how to consume each row, and how to act on the result. Return-value detail is a bonus rather than a gap since the output schema exists.

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 limit, offset and detail are already fully documented including the offset/sort interaction. The description adds nothing about pagination or detail levels, which is the expected baseline when the schema carries that load.

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

Purpose5/5

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

States a specific verb and resource at a defined scope: it sweeps the whole library for series whose metadata does not describe files on disk. It explicitly contrasts itself with the sibling fix_metadata, so an agent can pick between them without opening either schema.

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

Usage Guidelines5/5

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

Gives the exact routing rule: this is the discovery step fix_metadata cannot do because that tool needs a title, and a returned row's `service:itemId` is fed to fix_metadata as `id`. That is a full when-this/when-the-other plus the handoff between them.

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