Skip to main content
Glama
SavageCore
by SavageCore

seerr_delete_media

Destructive

Permanently delete a media item from Seerr to remove unwanted titles. This action is destructive and cannot be undone.

Instructions

Delete media item DESTRUCTIVE: this deletes data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
media_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, and the description merely repeats that it deletes data without adding context about irreversibility, scope, cascading effects, or permissions. It provides no behavioral insight beyond what the annotations already convey.

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

Conciseness2/5

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

The description is very short but includes redundancy: 'Delete media item' already implies deletion, and 'this deletes data' is repetitive. It is under-specified rather than effectively concise, lacking useful structure or elaboration.

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

Completeness2/5

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

For a destructive tool with a single parameter and no description of return values or side effects, the description is inadequate. It does not explain what is deleted, whether it is permanent, or what consequences occur (e.g., associated requests or files), making it unsafe for an agent to invoke confidently.

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

Parameters1/5

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

The input schema contains one parameter, media_id, with no description. The tool description does not elaborate on what media_id represents, its format, or how to obtain it. With 0% schema description coverage, the description should compensate but fails to do so.

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 states the verb 'Delete' and the resource 'media item', which distinguishes it from the sibling tool 'seerr_delete_media_file' by specifying a different object. However, it does not elaborate on what constitutes a 'media item' in this context, leaving some ambiguity.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, no exclusions, prerequisites, or context about when deletion is appropriate. The description simply states the action without any usage direction.

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/SavageCore/seerr-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server