Skip to main content
Glama

plex_search

Search your Plex media library with keyword, advanced filters, autocomplete suggestions, and saved searches. Retrieve recent searches or save complex filters for future use.

Instructions

Comprehensive search management tool for Plex Media Server.

PORTMANTEAU PATTERN RATIONALE: Consolidates 5 search modalities (text, advanced, suggest, history, persistence) into one tool to provide a unified discovery interface for all media types.

OPERATIONS:

  • search: Keyword-based text search across libraries.

  • advanced_search: Multi-parameter Boolean filtering (genre, year, actor, etc.).

  • suggest: Partial query autocomplete and suggestions.

  • recent_searches: Retrieve recent session search history.

  • save_search: Persist complex filters for future recall.

Return Format

{"success": bool, "data": dict|list, "operation": str, "count": int}

Examples

await plex_search(operation="search", query="star wars") await plex_search(operation="advanced_search", genre="comedy", year=2020) await plex_search(operation="suggest", query="incept")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoFilter by release year or list of years.
actorNoFilter by actor name or list.
genreNoFilter by genre name or list.
limitNoMaximum number of results to return.
queryNoSearch query string for keyword-based searches.
titleNoFilter by exact or partial title.
decadeNoFilter by decade (e.g. 1990 for 1990s).
offsetNoNumber of results to skip for pagination.
studioNoFilter by studio name or list.
countryNoFilter by country of origin or list.
sort_byNoSort field (titleSort, year, rating, etc.).titleSort
directorNoFilter by director name or list.
languageNoFilter by audio language or list.
max_yearNoMaximum release year.
min_yearNoMinimum release year.
sort_dirNoSort direction: asc or desc.asc
operationYesThe search operation to perform.
unwatchedNoFilter to only unwatched items.
collectionNoFilter by collection name or list.
library_idNoID of the library to search within.
max_ratingNoMaximum rating threshold (0.0-10.0).
max_recentNoMaximum number of recent searches to return.
media_typeNoFilter by media type (movie, episode, track).
min_ratingNoMinimum rating threshold (0.0-10.0).
search_nameNoName to save the search under for future recall.
content_ratingNoFilter by content rating (PG-13, R, etc.) or list.
summary_containsNoFilter items whose summary contains this text.
Behavior4/5

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

The description discloses mutating behavior via 'save_search: Persist complex filters for future recall' and provides a consistent return format. It aligns with annotations (readOnlyHint=false, destructiveHint=false) and adds operation-specific semantics without contradicting them.

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?

The description is structured with clear sections (RATIONALE, OPERATIONS, Return Format, Examples) and each section contributes useful information. The PORTMANTEAU PATTERN RATIONALE is somewhat verbose but aids understanding of the consolidation.

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?

For a tool with 5 operations and 27 parameters, the description gives a good overview with return format and examples. It could be more complete by specifying operation-specific parameter requirements (e.g., which parameters apply to which operation), but overall it's sufficient.

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?

The input schema provides descriptions for all 27 parameters, so the description need not add parameter-level details. The examples demonstrate usage of 'query' and 'genre'/'year', slightly enhancing understanding, but overall the description doesn't extend the schema's coverage.

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?

The description clearly states it's a 'Comprehensive search management tool for Plex Media Server' and enumerates five distinct operations (search, advanced_search, suggest, recent_searches, save_search), making its purpose unambiguous. It differentiates from sibling tools by focusing specifically on search operations across media types.

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

Usage Guidelines4/5

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

Each operation is briefly described (e.g., 'search: Keyword-based text search across libraries'), giving clear context for when to use that mode. However, it does not explicitly state when to prefer this tool over siblings like plex_media or plex_library, and no exclusions are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandraschi/plexmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server