Skip to main content
Glama
arr-mcps
by arr-mcps

seerr_users

Manage Seerr users: create, update, delete, list, and import users, plus handle settings, permissions, notifications, passwords, and linked Plex/Jellyfin accounts.

Instructions

seerr users operations on Seerr. Pass operation and an arguments dict matching that operation's parameters.

  • seerr_batch_update_users(body={}) — Update batch of users WRITE: this modifies your Seerr instance.

  • seerr_create_user(body={}) — Create new user WRITE: this modifies your Seerr instance.

  • seerr_create_user_settings_linked_accounts_jellyfin(user_id, body={}) — Link the provided Jellyfin account to the current user WRITE: this modifies your Seerr instance.

  • seerr_create_user_settings_linked_accounts_jellyfin_quickconnect(user_id, body={}) — Link Jellyfin/Emby account with Quick Connect WRITE: this modifies your Seerr instance.

  • seerr_create_user_settings_linked_accounts_plex(user_id, body={}) — Link the provided Plex account to the current user WRITE: this modifies your Seerr instance.

  • seerr_create_user_settings_main(user_id, body={}) — Update general settings for a user WRITE: this modifies your Seerr instance.

  • seerr_create_user_settings_notifications(user_id, body={}) — Update notification settings for a user WRITE: this modifies your Seerr instance.

  • seerr_create_user_settings_password(user_id, body={}) — Update password for a user WRITE: this modifies your Seerr instance.

  • seerr_create_user_settings_permissions(user_id, body={}) — Update permission settings for a user WRITE: this modifies your Seerr instance.

  • seerr_delete_user(user_id) — Delete user by ID DESTRUCTIVE: this deletes data.

  • seerr_delete_user_push_subscription(user_id, endpoint) — Delete user push subscription by key DESTRUCTIVE: this deletes data.

  • seerr_delete_user_settings_linked_accounts_jellyfin(user_id) — Remove the linked Jellyfin account for a user DESTRUCTIVE: this deletes data.

  • seerr_delete_user_settings_linked_accounts_plex(user_id) — Remove the linked Plex account for a user DESTRUCTIVE: this deletes data.

  • seerr_get_user(user_id) — Get user by ID

  • seerr_get_user_jellyfin(jellyfin_user_id) — Get user by Jellyfin user ID

  • seerr_get_user_push_subscription(user_id, endpoint) — Get web push notification settings for a user

  • seerr_get_user_quota(user_id) — Get quotas for a specific user

  • seerr_get_user_requests(user_id, take=None, skip=None) — Get requests for a specific user

  • seerr_get_user_settings_main(user_id) — Get general settings for a user

  • seerr_get_user_settings_notifications(user_id) — Get notification settings for a user

  • seerr_get_user_settings_password(user_id) — Get password page informatiom

  • seerr_get_user_settings_permissions(user_id) — Get permission settings for a user

  • seerr_get_user_watch_data(user_id) — Get watch data

  • seerr_get_user_watchlist(user_id, page=1) — Get the Plex watchlist for a specific user

  • seerr_import_jellyfin_users(body={}) — Import all users from Jellyfin WRITE: this modifies your Seerr instance.

  • seerr_import_plex_users(body={}) — Import all users from Plex WRITE: this modifies your Seerr instance.

  • seerr_list_user(take=None, skip=None, sort='created', sort_direction=None, q=None, include_ids=None) — Get all users

  • seerr_list_user_push_subscriptions(user_id) — Get all web push notification settings for a user

  • seerr_register_push_subscription(body={}) — Register a web push /user/registerPushSubscription WRITE: this modifies your Seerr instance.

  • seerr_update_user(user_id, body={}) — Update a user by user ID WRITE: this modifies your Seerr instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentsNo
operationYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description prominently labels each mutating operation with 'WRITE: this modifies your Seerr instance' and each destructive operation with 'DESTRUCTIVE: this deletes data.' This is significant behavioral disclosure, especially since no annotations are provided. It also clarifies which operations are read-only by omission. The description does not cover auth requirements or rate limits, but the key safety-relevant behavior is well-transparent.

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 a long list of 30 operations, but this is necessary given the tool's dispatcher design. It is well-structured with one operation per line, front-loaded with usage instructions. The repeated WRITE/DESTRUCTIVE phrases add clarity but are somewhat verbose; nevertheless, each sentence serves a purpose and there is no extraneous filler.

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 covering 30 operations, the description is quite complete: it names every operation, lists its parameters, and flags mutating/destructive behavior. It also notes the presence of an output schema elsewhere. Minor typos ('informatiom') and lack of detail about body contents are small gaps, but overall the description gives an agent enough information to select and invoke operations correctly.

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 only defines 'operation' and a generic 'arguments' dict, so the description carries the full burden for parameter semantics. It lists parameter names for each operation (e.g., user_id, take, skip) and even default values in some cases, which is valuable. However, body parameters are simply shown as 'body={}' with no explanation of their structure, leaving significant ambiguity for operations that require request bodies.

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 identifies the tool as a dispatcher for Seerr user operations, with an explicit instruction to pass 'operation' and 'arguments'. The list of 30 sub-operations provides concrete details about available actions, making the purpose clear and specific. However, the initial phrasing 'seerr users operations' is somewhat generic and relies on the list to fully convey the scope.

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 implicitly guides usage by enumerating every operation with its parameters, and the tool name indicates it covers user-related tasks. However, it does not explicitly state when to prefer this tool over sibling tools (e.g., seerr_requests) or mention any exclusions. Usage context is implied rather than explicitly articulated.

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/arr-mcps/seerr-mcp'

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