arr-mcp

Overview Schema Source Related Servers Discussions Admin

Missing and upgradable

get_wanted

Read-only

List monitored movies, series, or artists that are missing files or below their quality cutoff, using missing or upgradable scope across Radarr, Sonarr, and Lidarr.

Instructions

Radarr, Sonarr and Lidarr's own wanted lists. scope is required: "missing" is monitored items with no file, "upgradable" monitored items with a file below the profile's quality cutoff. Unlike get_library it lists missing episodes one by one. Sonarr rows carry season, episode and episodeTitle; Lidarr rows are kind: "artist" with albumId and albumTitle, and albumId is what set_monitoring takes with level: "album". On Lidarr an album missing any track counts as missing, so it can be in both lists, and albums of an unmonitored artist are left out. Unmonitored gaps never appear. detail: "minimal" drops titles and air dates. Field reference: arr://docs/get_wanted.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum items to return. Defaults to 50, hard maximum 500.
`scope`	Yes	`missing`: monitored items with no file at all (on Lidarr, an album with any track missing). `upgradable`: monitored items that have a file but not yet at the quality profile's cutoff. Required — the two answer different questions, and a default would silently hide one of them.
`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.
`service`	No	Scope to one service.
`instance`	No	Which instance (e.g. "4k") when several of this service exist. Omit it when there is one.

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.

Changed19 schema fields changedv1.74.0Nov 9, 2026

removedInput schema / $schema

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

changedInput schema / properties / instance / description

Previous value: -"Which instance, when several of this service are configured — for example \"4k\" or \"hd\". Omit it when there is only one. If several are configured and you omit it, the call is refused and the names are listed."New value: +"Which instance (e.g. \"4k\") when several of this service exist. Omit it when there is one."

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
```

changedInput schema / properties / service / enum

Previous value: -[
-  "radarr",
-  "sonarr",
-  "whisparr",
-  "lidarr",
-  "prowlarr",
-  "bazarr",
-  "jellyfin",
-  "seerr",
-  "sabnzbd",
-  "nzbget",
-  "transmission",
-  "qbittorrent",
-  "plex",
-  "profilarr",
-  "cleanuparr",
-  "reclaimerr",
-  "dispatcharr",
-  "shelfmark",
-  "grimmory"
-]New value: +[
+  "radarr",
+  "sonarr",
+  "lidarr"
+]

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

Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds substantial behavior: Lidarr albums missing any track can appear in both lists, unmonitored gaps are excluded, and `detail: "minimal"` drops titles and air dates. It also points to arr://docs/get_wanted for the field reference, though it does not discuss pagination stability beyond the schema's own note.

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-loads the core purpose and scope definitions, then layers service-specific caveats. Dense but nearly every sentence carries distinct information; the field-reference pointer is a small extra that could be trimmed.

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?

With an output schema present, return values need not be explained, and the description covers the remaining complexity: scope semantics, per-service row shapes, Lidarr dual-list behavior, and detail levels. Nothing an agent needs to call it correctly is missing.

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 beyond the schema: it links Lidarr `albumId` to set_monitoring with `level: "album"` and explains the consequence of `detail: "minimal"`. The `service`/`instance`/`limit`/`offset` semantics are left to the schema.

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 resource (Radarr/Sonarr/Lidarr wanted lists) and defines the two scopes precisely: missing = monitored with no file, upgradable = file below quality cutoff. It explicitly distinguishes itself from the sibling get_library by noting it lists missing episodes one by one.

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 explicit selection criteria for `scope` (the two answer different questions), names the alternative get_library and how it differs, and states exclusions such as unmonitored gaps never appearing and unmonitored artists' albums being left out. An agent can pick this tool and the right scope without inference.

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