arr-doctor

bulk_edit_preview

Read-only

Preview bulk changes to Sonarr series or Radarr movies before applying: see matching items, what would change, and get a token to apply if approved.

Instructions

Preview a change to many series or movies at once (monitoring, quality profile, tags, series type, minimum availability): which items match and what would change. Changes nothing. Select items by IDs/titles and/or filters (status, monitored, quality profile, tag, year, complete). Show the preview to the user; if they agree, apply it with bulk_edit_apply and the confirmation_token returned here.

Examples: "Which ended series would be unmonitored?", "Preview putting the 4K profile on all 2024 movies"

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Filter: has this tag
`items`	No	Series/movie IDs or titles to edit
`status`	No	Filter by status. Sonarr: continuing, ended, upcoming. Radarr: announced, inCinemas, released
`service`	Yes	'sonarr' (series) or 'radarr' (movies)
`year_to`	No	Filter: year <= this
`add_tags`	No	Change: tags to add (created if missing)
`complete`	No	Filter: all episodes on disk (series) / has file (movies)
`monitored`	No	Filter: currently monitored or not
`year_from`	No	Filter: year >= this
`remove_tags`	No	Change: tags to remove
`set_monitored`	No	Change: monitor or unmonitor
`quality_profile`	No	Filter: current quality profile name or ID
`set_series_type`	No	Change (Sonarr)
`set_quality_profile`	No	Change: new quality profile name or ID
`set_minimum_availability`	No	Change (Radarr)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations declare readOnlyHint=true, and the description reinforces this with 'Changes nothing'. It adds behavior beyond annotations by explaining the confirmation_token return and the required follow-up with bulk_edit_apply.

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

Conciseness5/5

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

Front-loads the purpose and the key 'Changes nothing' safety statement, then gives selection guidance, workflow, and concise examples. Every sentence earns its place.

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 complex 15-parameter preview tool, the description covers selection modes, change types, the read-only guarantee, the confirmation_token output, and the sibling apply tool. With an output schema also present, nothing important is missing.

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?

Schema description coverage is 100%, so the schema already documents all 15 parameters in detail. The description groups parameters into selection filters and changes, but does not add per-parameter meaning beyond what the schema provides.

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?

States a specific verb and resource: preview a bulk change to series or movies. It distinguishes itself from the sibling bulk_edit_apply by saying it changes nothing and is only a preview.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to show the preview to the user and then apply with bulk_edit_apply using the returned confirmation_token. This gives both the workflow and the alternative tool, leaving no ambiguity about when to use this tool.

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