Skip to main content
Glama

Delete an indexer

delete_indexer
Destructive

Deletes a Prowlarr indexer and its settings across every synced app, after a preview names failing copies. Irreversible; disable the indexer instead to stop grabs.

Instructions

Deletes one Prowlarr indexer and its settings, and its copy in each app Prowlarr syncs to; apps with sync off keep a failing copy, and the preview names them. Not undoable; to stop grabs reversibly, use manage_indexer disable. Fails on an unknown id. Previews first; confirm to apply it.

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": {
      "id": "<id>"
    },
    "name": "delete_indexer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe indexer id from get_indexers: 21 for a row shown as prowlarr:21.
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.
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.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds real context beyond them: the deletion propagates to synced apps, sync-disabled apps retain a failing copy that the preview names, the action is not undoable, and unknown ids fail. That is exactly the pre-flight information a destructive tool needs.

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 the operation and its blast radius, and every clause carries information (propagation, irreversibility, failure mode, preview flow). The opening sentence runs long with stacked commas, which slightly reduces readability.

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 destructive, sync-propagating operation the description covers irreversibility, side effects, failure behavior, the preview/confirm protocol, and a reversible alternative. An output schema exists, so return-shape detail is correctly omitted.

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?

Schema coverage is 100%, so the schema already explains id, confirm, dry_run, and instance — baseline would be 3. The description adds the workflow meaning behind `confirm` ("Previews first; confirm to apply it") that the schema's one-line token note does not convey, though it says nothing extra about `instance`.

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 ("Deletes one Prowlarr indexer and its settings") and then extends the scope precisely — copies in each synced app, with sync-off apps left failing. It also names the sibling it is not (manage_indexer `disable`), so the agent can distinguish it without opening another schema.

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 routes the reversible case to manage_indexer `disable`, states when to use dry_run ("for what if questions, not the first step of a change"), and describes the preview-then-confirm sequence. Both when-to-use and when-not-to-use are covered.

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