Skip to main content
Glama

plex_user

Manage Plex Media Server user accounts and access: list, get, create, update, delete, and set permissions for shared libraries.

Instructions

Comprehensive user management operations for Plex Media Server.

PORTMANTEAU PATTERN RATIONALE: Consolidates 6 user and access control operations into a single interface to ensure consistent security policy enforcement across shared libraries.

Return Format

ToolResult with content dict: {"success": bool, "operation": str, "data": {...}}

Examples

await plex_user(operation="list") await plex_user(operation="get", user_id="123") await plex_user(operation="create", username="newuser", email="user@example.com", password="secret1234")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoUser role assignment.
emailNoEmail address for create/update operations.
user_idNoTarget user ID for scoped operations.
passwordNoPassword for create/update operations (min 8 chars).
usernameNoUsername for create/update operations.
operationYesUser management operation to execute.
restrictedNoRestrict user to specific libraries.
permissionsNoPermission dict with keys like allowSync, restricted.
Behavior1/5

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

The annotations declare destructiveHint=false, yet the schema includes a 'delete' operation, and the description mentions consolidating user and access control operations, which implicitly includes delete. This is a contradiction between the described capability and the annotation. The description also does not clarify side effects, irreversibility, or permission requirements for mutations, leaving a transparency gap beyond the contradiction.

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 well-structured with a clear initial purpose, a rationale section, return format, and examples. It is concise enough but includes a somewhat verbose 'PORTMANTEAU PATTERN RATIONALE' that is not strictly necessary for usage. The front-loaded purpose sentence helps the agent quickly identify the tool's scope.

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

Completeness3/5

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

Given the tool has 8 parameters, 6 operations, and no output schema, the description provides some necessary context (return format, examples) but omits operation-specific behavior, such as which operations require auth, the structure of the 'data' dict, or error cases. The annotation contradiction and lack of per-operation detail mean the description is not fully complete for an agent to use the tool confidently in all scenarios.

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 100% description coverage for all 8 parameters, so the schema carries the primary semantic burden. The description adds a few examples showing typical parameter combinations (e.g., create with username/email/password), which is helpful but not extensive. Overall, the description offers marginal value over the schema's existing parameter descriptions.

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 that the tool handles "Comprehensive user management operations for Plex Media Server" and consolidates "6 user and access control operations." This distinguishes it from sibling tools like plex_library or plex_media, which focus on other domains. The purpose is clear but lacks a single specific verb; it is a portmanteau tool with varied operations.

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?

The description provides a rationale for consolidating operations to ensure "consistent security policy enforcement across shared libraries," which implies it is the go-to tool for user management. However, it does not explicitly state when to use it versus alternatives or when not to use it. Examples illustrate common operations but do not clarify exclusions or alternative tools.

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