Overseerr MCP Server

search_media

Search movies and TV shows using single, batch, or dedupe modes. Dedupe mode returns availability status to guide batch processing.

Instructions

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Page number
`limit`	No	Max results
`query`	No	Single search query
`format`	No	Response format	compact
`titles`	No	Titles to check (dedupe mode)
`queries`	No	Multiple search queries (batch mode)
`language`	No	Language code	en
`dedupeMode`	No	Batch dedupe with availability check
`autoRequest`	No	Auto-request passing items (requires dedupeMode)
`autoNormalize`	No	Strip "Season N"/"Part N" from titles
`includeDetails`	No	Add details to dedupe results (dedupe only)
`requestOptions`	No	AutoRequest options
`checkAvailability`	No	Check status (slower, fetches per-result details)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.1.3May 20, 2026
Removedv2.1.2May 10, 2026

Changed14 schema fields changedv1.0.0Jan 3, 2026

addedInput schema / properties / autoNormalize

Added value: +{
+  "default": false,
+  "description": "Strip \"Season N\"/\"Part N\" from titles",
+  "type": "boolean"
+}

addedInput schema / properties / autoRequest

Added value: +{
+  "default": false,
+  "description": "Auto-request passing items (requires dedupeMode)",
+  "type": "boolean"
+}

addedInput schema / properties / checkAvailability

Added value: +{
+  "default": false,
+  "description": "Check status (slower, fetches per-result details)",
+  "type": "boolean"
+}

addedInput schema / properties / dedupeMode

Added value: +{
+  "default": false,
+  "description": "Batch dedupe with availability check",
+  "type": "boolean"
+}

addedInput schema / properties / format

Added value: +{
+  "default": "compact",
+  "description": "Response format",
+  "enum": [
+    "compact",
+    "standard",
+    "full"
+  ],
+  "type": "string"
+}

addedInput schema / properties / includeDetails

Added value: +{
+  "description": "Add details to dedupe results (dedupe only)",
+  "properties": {
+    "fields": {
+      "description": "Basic: mediaType,year,posterPath | Standard: rating,overview,genres,runtime | TV: numberOfSeasons,numberOfEpisodes,seasons | Advanced: releaseDate,firstAirDate,originalTitle,originalName,popularity,backdropPath,homepage,status,tagline | Availability: mediaStatus,hasRequests,requestCount | targetSeason auto-adds for season numbers",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "includeSeason": {
+      "default": true,
+      "description": "Auto-add targetSeason for TV with season in title",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

changedInput schema / properties / language / description

Previous value: -"Language code (e.g., \"en\", default: \"en\")"New value: +"Language code"

addedInput schema / properties / limit

Added value: +{
+  "description": "Max results",
+  "type": "number"
+}

changedInput schema / properties / page / description

Previous value: -"Page number for pagination (default: 1)"New value: +"Page number"

addedInput schema / properties / queries

Added value: +{
+  "description": "Multiple search queries (batch mode)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / query / description

Previous value: -"Search query (movie/TV show/person name)"New value: +"Single search query"

addedInput schema / properties / requestOptions

Added value: +{
+  "description": "AutoRequest options",
+  "properties": {
+    "dryRun": {
+      "default": false,
+      "description": "Preview only",
+      "type": "boolean"
+    },
+    "is4k": {
+      "default": false,
+      "description": "Request 4K",
+      "type": "boolean"
+    },
+    "profileId": {
+      "type": "number"
+    },
+    "rootFolder": {
+      "type": "string"
+    },
+    "seasons": {
+      "description": "TV seasons. \"all\"=no season 0 (specials); [0,1,2]=with specials",
+      "oneOf": [
+        {
+          "items": {
+            "type": "number"
+          },
+          "type": "array"
+        },
+        {
+          "enum": [
+            "all"
+          ],
+          "type": "string"
+        }
+      ]
+    },
+    "serverId": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / titles

Added value: +{
+  "description": "Titles to check (dedupe mode)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / required
```
Removed value: -[
-  "query"
-]
```

First observedNov 3, 2025

TDQS

C2.9/5.0

Behavior2/5

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

Without annotations, the description should fully disclose behavior. It mentions dedupe returns actionable statuses but fails to indicate if tool triggers requests (autoRequest) or is read-only. No side effects or auth needs disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise: two sentences covering purpose and dedupe statuses. No redundant information; every word earns its place.

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

Completeness2/5

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

Despite 13 parameters and no output schema, description omits output format for single/batch modes, mode selection criteria, and how to interpret results beyond dedupe. Incomplete for complex tool.

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 coverage is 100%, so baseline is 3. The description adds context about dedupe statuses but does not significantly enhance parameter understanding beyond what schema descriptions provide.

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 clearly states 'Search movies/TV with single/batch/dedupe modes,' specifying the verb 'Search' and resource 'movies/TV.' It distinguishes from siblings like manage_media_requests or request_media, which involve different actions.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., get_media_details for details, request_media for requesting). The description lacks when-not usage or explicit context for choosing modes.

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

Deploy Server

search_media

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools