Skip to main content
Glama
arr-mcps

seerr-mcp

by arr-mcps
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

seerr_settings_notifications

Configure Seerr notifications: update or test settings for Discord, email, Slack, Telegram, webhook, Pushover, and more, or retrieve current configurations.

Instructions

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

  • seerr_create_settings_notifications_discord(body={}) — Update Discord notification settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_discord_test(body={}) — Test Discord settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_email(body={}) — Update email notification settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_email_test(body={}) — Test email settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_gotify(body={}) — Update Gotify notification settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_gotify_test(body={}) — Test Gotify settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_ntfy(body={}) — Update ntfy.sh notification settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_ntfy_test(body={}) — Test ntfy.sh settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_pushbullet(body={}) — Update Pushbullet notification settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_pushbullet_test(body={}) — Test Pushbullet settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_pushover(body={}) — Update Pushover notification settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_pushover_test(body={}) — Test Pushover settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_slack(body={}) — Update Slack notification settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_slack_test(body={}) — Test Slack settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_telegram(body={}) — Update Telegram notification settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_telegram_test(body={}) — Test Telegram settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_webhook(body={}) — Update webhook notification settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_webhook_test(body={}) — Test webhook settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_webpush(body={}) — Update Web Push notification settings WRITE: this modifies your Seerr instance.

  • seerr_create_settings_notifications_webpush_test(body={}) — Test Web Push settings WRITE: this modifies your Seerr instance.

  • seerr_list_pushover_sounds(token) — Get Pushover sounds

  • seerr_list_settings_notifications_discord() — Get Discord notification settings

  • seerr_list_settings_notifications_email() — Get email notification settings

  • seerr_list_settings_notifications_gotify() — Get Gotify notification settings

  • seerr_list_settings_notifications_ntfy() — Get ntfy.sh notification settings

  • seerr_list_settings_notifications_pushbullet() — Get Pushbullet notification settings

  • seerr_list_settings_notifications_pushover() — Get Pushover notification settings

  • seerr_list_settings_notifications_slack() — Get Slack notification settings

  • seerr_list_settings_notifications_telegram() — Get Telegram notification settings

  • seerr_list_settings_notifications_webhook() — Get webhook notification settings

  • seerr_list_settings_notifications_webpush() — Get Web Push notification settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentsNo
operationYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A3.8/5.0
Behavior3/5

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

The description flags each create/test operation as 'WRITE: this modifies your Seerr instance,' disclosing mutating behavior. Since no annotations are provided, this is valuable transparency. However, it omits other behavioral details such as auth requirements, side effects of test operations, or error behavior, so transparency is partial.

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 front-loaded with a concise usage instruction and then provides an exhaustive list of operations, which is necessary for a router tool. But the repeated 'WRITE: this modifies your Seerr instance.' is verbose and could be consolidated, though it does ensure each write operation is flagged.

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?

For a complex tool with 31 operations, the description enumerates all operations and indicates their input parameters at a high level. It relies on the output schema for return values. However, it lacks examples, error handling notes, and details about how `arguments` should map to each operation, making it slightly incomplete.

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?

With schema coverage at 0%, the description compensates by listing operation signatures (e.g., `body={}`, `token`) that imply what the `arguments` dict should contain. Nevertheless, it does not specify the exact shape of `body` or fields for each operation, leaving the agent to infer parameter structure from names alone.

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 identifies the tool as a dispatcher for Seerr notification settings operations, listing all 31 possible operations with their names and brief purpose. It distinguishes from sibling tools like seerr_settings_general by focusing specifically on notification settings. The phrase 'operations on Seerr' is generic but accompanied by exhaustive enumeration.

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?

It provides explicit usage instructions: 'Pass `operation` and an `arguments` dict matching that operation's parameters.' This tells the agent how to invoke the tool. However, it does not state when to prefer this tool over siblings or mention alternatives, though the operation list implies coverage of all notification settings operations.

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