Skip to main content
Glama

Blocklist a title

blocklist_media
Destructive

Adds or removes a title from Seerr's blocklist or an *arr's import exclusions, with a preview and confirm before applying, to stop unwanted requests and imports.

Instructions

Adds a title to, or removes it from, Seerr's blocklist (nobody can request it) or, with service, an *arr's import exclusions (only its own import lists skip it). delete_media's seerr_blocklist adds to Seerr while deleting. Removing from Seerr is destructive: it also deletes the title's requests and issues. Previews first; confirm to apply.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>",
      "id": "<id>"
    },
    "name": "blocklist_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe title's TMDB id (seerr, radarr), TVDB id (sonarr) or MusicBrainz artist id (lidarr), from `ids` on a search_media or get_media_details record.
kindNoSeerr only, where it is required.
actionYesadd, or remove (on Seerr destructive: it also deletes its record of the title).
confirmNoThe token from this tool's preview; pass it back to apply.
dry_runNoPreview only, no token issued: for "what if" questions, not the first step of a change.
serviceNoseerr
instanceNoWhich instance (e.g. "4k") when several of this service exist. Omit it when there is one.

Output Schema

NameRequiredDescriptionDefault
noopYes
tierYes
toolYes
targetYes
appliedYes
dry_runYes
effectsYes
serviceYes
summaryYes
operationYes
permissionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv2.2.0
    • changedInput schema / properties / confirm / description
      Previous value: -"The token from this tool's preview, passed back verbatim to apply it. Single-use and bound to the previewed arguments."New value: +"The token from this tool's preview; pass it back to apply."
    • changedInput schema / properties / dry_run / description
      Previous value: -"Preview without a confirm token, for \"what would happen if\" questions; not the first step of a real change."New value: +"Preview only, no token issued: for \"what if\" questions, not the first step of a change."
    • removedOutput schema / properties / audit_id
      Removed value: -{
      -  "type": "number"
      -}
    • removedOutput schema / properties / confirm_error
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / confirm_token
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / next_steps
      Removed value: -{
      -  "items": {
      -    "additionalProperties": {},
      -    "properties": {
      -      "arguments": {
      -        "additionalProperties": {},
      -        "properties": {},
      -        "type": "object"
      -      },
      -      "tool": {
      -        "type": "string"
      -      },
      -      "why": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "tool",
      -      "arguments",
      -      "why"
      -    ],
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
    • removedOutput schema / properties / permission / properties / reason
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / permission / properties / remedy
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / result
      Removed value: -{}
    • removedOutput schema / properties / unchecked
      Removed value: -{
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • removedOutput schema / properties / warnings
      Removed value: -{
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
  2. Addedv1.84.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare destructiveHint=true, and the description goes well beyond that by naming exactly what is destroyed on Seerr removal (the title's requests and issues), and by clarifying that *arr removal is non-destructive in comparison. It also discloses the two-phase preview-then-confirm protocol, which is critical behavioral context for a mutation tool.

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?

Front-loaded with purpose and mechanism, then consequences, then the confirm requirement — a sensible ordering. The parenthetical asides are dense but each carries genuine semantic payload; nothing is redundant with the schema.

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

Completeness5/5

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

For a 7-parameter destructive mutation tool, the description covers the mechanism, the destructive consequence, the alternative tool, and the confirmation workflow; the output schema handles return values and the input schema handles field-level detail. Nothing an agent needs before calling is absent.

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

Parameters4/5

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

With 86% schema coverage the baseline is already 3, and the description adds real meaning: `service` selects between two different blocking mechanisms with different blast radii, and `confirm` is tied to the preview token flow. It does not restate `kind`, `instance`, or `dry_run` semantics, which the schema already documents.

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 states a specific verb pair (adds/removes) and two distinct resources with their exact semantics: Seerr's blocklist ('nobody can request it') versus an *arr's import exclusions ('only its own import lists skip it'). It also explicitly differentiates itself from delete_media's `seerr_blocklist` path, so an agent can pick the right tool without opening schemas.

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 gives clear routing context by contrasting with delete_media's combined delete-and-blocklist behavior, and states the workflow ('Previews first; confirm to apply'). What's missing is explicit guidance on when to use this versus the sibling blocklist readers/removers (get_blocklist, remove_blocklist_item) — though the add/remove action enum largely covers that.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.