Skip to main content
Glama

radarr_delete_customformat

Destructive

Delete a custom format from Radarr by its ID. This destructive action removes the format permanently, helping clear out obsolete or unwanted definitions.

Instructions

Delete custom formats. DESTRUCTIVE: this deletes data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

The description repeats the destructiveHint annotation ('this deletes data') without adding contextual detail such as permanence, required permissions, or effects on related records. Since annotations already disclose the destructive nature, the description adds no new behavioral insight.

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 very short and front-loaded, but the second sentence redundantly repeats the destructive annotation. It remains concise, though not entirely waste-free.

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 undocumented parameter and no usage guidance, the description is inadequate. It fails to specify what the id identifies, irreversible consequences, or alternative bulk operations, even though the tool complexity is low.

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

Parameters2/5

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

With schema description coverage at 0%, the description should compensate for the undocumented 'id' parameter. It fails to explicitly state that 'id' is the identifier of the custom format to delete. While the parameter name is self-explanatory, the description provides no direct clarification.

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 clearly states 'Delete custom formats' with a specific verb and resource. However, it does not explicitly distinguish this single-delete tool from the sibling radarr_bulk_delete_customformat, relying on the tool name and singular id parameter to imply the difference.

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. The description does not mention that this deletes a single custom format by id, nor does it reference bulk deletion as an alternative. The only usage-related information is the destructive warning, which duplicates the annotation.

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/radarr-mcp'

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