arr-mcp

Overview Schema Source Related Servers Discussions Admin

Requests

get_requests

Read-only

Retrieve a user's media requests—pending, approved, or declined—with filtering, pagination, and optional issue details to review playback problems and user reports.

Instructions

Media requests in Seerr — pending, approved or declined — for one user. Defaults to the configured user; reading another requires allow_other_users. At detail: "full" it also returns issues: what your users have reported as broken (video, audio, subtitle), each with its newest comments. Issues are everyone's, not just this user's, and a Seerr that cannot answer for them still answers for the requests.

Input Schema

Name	Required	Description	Default
`user`	No	Whose playback to read. Defaults to the configured default_user; any other value requires allow_other_users.
`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.
`status`	No	Only requests in this state. Omit for all.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 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 / issues / description

Removed value: -"What users reported as broken. Only at `detail: \"full\"`."

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

A3.8/5.0

Behavior4/5

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

Beyond the readOnlyHint annotation it discloses an authorization prerequisite (allow_other_users), the default-user behavior, and a graceful-degradation trait — issues may fail while requests still succeed. That partial-failure note is genuinely non-obvious behavior an agent needs. It stops short of 5 because pagination stability and ordering are left entirely to the schema.

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?

Three tight sentences, front-loaded with resource and scope before the detail-level caveat. The closing clause about a Seerr that cannot answer for issues is a little convoluted but carries real information, so it earns its place.

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?

An output schema exists, so return values need no explanation; the description covers the pieces the schema cannot — permission requirements, defaulting, and the issues side-channel. For a five-parameter read tool with full schema coverage and annotations, this is close to complete.

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 description coverage is 100%, so the baseline is 3; the description earns an extra point by explaining what 'full' detail actually adds (issues with newest comments) and by clarifying that issues span all users, not just the requested one. The user/allow_other_users wording duplicates the schema rather than extending it.

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 (media requests in Seerr) and its scope (one user, states pending/approved/declined), which lets an agent distinguish this read tool from the mutating siblings respond_to_request and delete_request. The verb is only implied by the tool name rather than stated outright, which keeps it just short of a 5.

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 useful context — defaults to the configured user, reading another needs allow_other_users — and signals that no separate issues call is needed when detail is 'full'. It never explicitly states when to prefer this over get_media_details, get_metadata_issues, or the request-mutation siblings, so routing still requires inference.

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