Skip to main content
Glama

create_playlist

Create a Plex playlist by providing a title and type. For regular playlists, include ratingKeys; for smart playlists, set smart=true and specify librarySectionId and filter.

Instructions

Create a new Plex playlist (requires PLEX_ENABLE_MUTATIVE_OPS=true). For regular playlists, ratingKeys is required — Plex does not support creating empty playlists. For smart playlists, set smart=true and provide librarySectionId (and optionally libtype / smartFilter).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesPlaylist type (video, audio, photo) or media type (movie, show, episode, artist, album, track)
smartNoCreate a smart playlist filtered from a library section (default: false)
titleYesPlaylist title
libtypeNoSmart playlists only: content type to filter for. Defaults based on playlist type (audio->track, video->movie, photo->photo).
ratingKeysNoRating keys to seed the playlist with. REQUIRED for non-smart playlists (>=1). All items are sent in a single POST, comma-joined in the playlist URI. Mutually exclusive with smart=true.
smartFilterNoSmart playlists only: raw Plex filter query string, e.g. 'genre=Drama&year>=2020&sort=titleSort:asc&limit=100'. Appended to the section URI.
librarySectionIdNoSmart playlists only: library section ID to filter (e.g. '1'). REQUIRED when smart=true.
Behavior4/5

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

Discloses the critical requirement for mutative ops, explains Plex's limitation on empty playlists, and clarifies the mutual exclusivity of smart vs ratingKeys. With no annotations, this description carries the burden well.

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?

Three sentences pack substantial meaning: purpose, precondition, and two branches with conditions. No redundant phrases.

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?

Covers both regular and smart playlist variations comprehensively, including dependencies and prerequisites. Could optionally mention return values but not essential for correct invocation given the tool's create-only role.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Description enriches schema by explaining dependencies: ratingKeys required for non-smart, librarySectionId required for smart, and the example smartFilter query syntax. Adds behavioral context beyond property descriptions.

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?

Specific verb 'create' + resource 'Plex playlist' immediately clarifies action. Distinguishes from sibling tools like delete_playlist, add_to_playlist, and get_playlists through explicit context.

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?

Clearly states prerequisites (PLEX_ENABLE_MUTATIVE_OPS) and the two distinct creation modes with their requirements. While it doesn't explicitly list alternatives, the regular vs smart playlist distinction provides clear conditional use.

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/niavasha/plex-mcp-server'

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