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

seerr_settings_general

Manage Seerr settings and discover sliders. Perform create, read, update, delete, test, and sync actions for Plex, Jellyfin, Radarr, Sonarr, Tautulli, and network configurations.

Instructions

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

  • seerr_add_discover_slider(body={}) — Add a new slider WRITE: this modifies your Seerr instance.

  • seerr_cancel_job(job_id) — Cancel a specific job WRITE: this modifies your Seerr instance.

  • seerr_create_settings_jellyfin(body={}) — Update Jellyfin settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_jellyfin_sync(body={}) — Start full Jellyfin library sync WRITE: this modifies your Seerr instance.

  • seerr_create_settings_main(body={}) — Update main settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_metadatas_test(body={}) — Test Provider configuration WRITE: this modifies your Seerr instance.

  • seerr_create_settings_network(body={}) — Update network settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_plex(body={}) — Update Plex settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_plex_sync(body={}) — Start full Plex library scan WRITE: this modifies your Seerr instance.

  • seerr_create_settings_radarr(body={}) — Create Radarr instance WRITE: this modifies your Seerr instance.

  • seerr_create_settings_radarr_test(body={}) — Test Radarr configuration WRITE: this modifies your Seerr instance.

  • seerr_create_settings_sonarr(body={}) — Create Sonarr instance WRITE: this modifies your Seerr instance.

  • seerr_create_settings_sonarr_test(body={}) — Test Sonarr configuration WRITE: this modifies your Seerr instance.

  • seerr_create_settings_tautulli(body={}) — Update Tautulli settings WRITE: this modifies your Seerr instance.

  • seerr_delete_discover_slider(slider_id) — Delete slider by ID DESTRUCTIVE: this deletes data.

  • seerr_delete_settings_radarr(radarr_id) — Delete Radarr instance DESTRUCTIVE: this deletes data.

  • seerr_delete_settings_sonarr(sonarr_id) — Delete Sonarr instance DESTRUCTIVE: this deletes data.

  • seerr_flush_cache(cache_id) — Flush a specific cache WRITE: this modifies your Seerr instance.

  • seerr_flush_dns_cache(dns_entry) — Flush a specific DNS cache entry WRITE: this modifies your Seerr instance.

  • seerr_get_settings_radarr_profiles(radarr_id) — Get available Radarr profiles

  • seerr_initialize_app() — Initialize application WRITE: this modifies your Seerr instance.

  • seerr_list_discover_sliders() — Get all discover sliders

  • seerr_list_settings_about() — Get server stats

  • seerr_list_settings_cache() — Get a list of active caches

  • seerr_list_settings_jellyfin() — Get Jellyfin settings

  • seerr_list_settings_jellyfin_library(sync=None, enable=None) — Get Jellyfin libraries

  • seerr_list_settings_jellyfin_sync() — Get status of full Jellyfin library sync

  • seerr_list_settings_jellyfin_users() — Get Jellyfin Users

  • seerr_list_settings_jobs() — Get scheduled jobs

  • seerr_list_settings_logs(take=None, skip=None, filter='debug', search=None) — Returns logs

  • seerr_list_settings_main() — Get main settings

  • seerr_list_settings_metadatas() — Get Metadata settings

  • seerr_list_settings_network() — Get network settings

  • seerr_list_settings_plex() — Get Plex settings

  • seerr_list_settings_plex_devices_servers() — Gets the user's available Plex servers

  • seerr_list_settings_plex_library(sync=None, enable=None) — Get Plex libraries

  • seerr_list_settings_plex_sync() — Get status of full Plex library scan

  • seerr_list_settings_plex_users() — Get Plex users

  • seerr_list_settings_public() — Get public settings

  • seerr_list_settings_radarr() — Get Radarr settings

  • seerr_list_settings_sonarr() — Get Sonarr settings

  • seerr_list_settings_tautulli() — Get Tautulli settings

  • seerr_regenerate_api_key() — Get main settings with newly-generated API key WRITE: this modifies your Seerr instance.

  • seerr_reset_discover_sliders() — Reset all discover sliders (WRITE — a GET that mutates state)

  • seerr_run_job(job_id) — Invoke a specific job WRITE: this modifies your Seerr instance.

  • seerr_schedule_job(job_id, body={}) — Modify job schedule WRITE: this modifies your Seerr instance.

  • seerr_update_discover_slider(slider_id, body={}) — Update a single slider WRITE: this modifies your Seerr instance.

  • seerr_update_discover_sliders(body=[]) — Batch update all sliders. WRITE: this modifies your Seerr instance.

  • seerr_update_settings_metadatas(body={}) — Update Metadata settings WRITE: this modifies your Seerr instance.

  • seerr_update_settings_radarr(radarr_id, body={}) — Update Radarr instance WRITE: this modifies your Seerr instance.

  • seerr_update_settings_sonarr(sonarr_id, body={}) — Update Sonarr instance 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?

With no annotations, the description takes on the role of disclosing side effects: it labels every mutating sub-operation as 'WRITE: this modifies your Seerr instance' and deletions as 'DESTRUCTIVE: this deletes data.' It even flags the unusual seerr_reset_discover_sliders as 'WRITE — a GET that mutates state,' showing good behavioral transparency, though it does not cover auth or rate limits.

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

Conciseness3/5

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

The description front-loads the core instruction and uses a structured bullet list, which is appropriate for a 52-operation dispatcher. But the repeated suffix 'WRITE: this modifies your Seerr instance' appears on many lines and could be stated once, making the description longer than necessary.

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's complexity, the description is a fairly complete catalog of all sub-operations and their side effects, and an output schema exists so return values need not be described. Yet it omits detailed argument semantics and any relation to sibling settings tools, so agents can select an operation but may still struggle to construct valid body arguments.

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 specifies operation and a generic arguments dict (0% schema coverage), so the inline signatures like seerr_add_discover_slider(body={}) and seerr_cancel_job(job_id) add parameter names and defaults beyond the schema. However, it does not explain what body should contain or the meaning of each parameter, leaving substantial ambiguity for nested body arguments.

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 opens by defining the tool as 'seerr settings general operations on Seerr' and then enumerates all supported sub-operations, making clear this is a dispatcher for Seerr settings. It is specific about the resource and action, but it does not explicitly differentiate from the sibling seerr_settings_notifications tool, relying on the operation list to imply 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?

It provides a direct invocation instruction: 'Pass operation and an arguments dict matching that operation's parameters,' which tells the agent how to call the tool. However, it does not give when-to-use guidance versus sibling tools like seerr_settings_notifications or any explicit exclusions, so usage context is only implied by the operation list.

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