Delete a notification by its ID to remove it from Prowlarr. Provide the unique notification ID to permanently remove the configured alert.
Delete Notification.
DELETE /api/v1/notification/{id}
Args: id: Path parameter.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description merely restates 'Delete Notification' and the endpoint, adding no behavioral context beyond what annotations already declare (destructiveHint, idempotentHint). It does not mention permanence, cascading effects, permissions, or failure behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded with the action. It includes only the endpoint, a short arg note, and no filler. The HTTP line is somewhat redundant with the tool name but still useful for invocation.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple single-parameter delete operation, output schema, and annotations, the description is largely sufficient to invoke the tool. However, it lacks usage context and offers no warning beyond the existing destructiveHint annotation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% description coverage, so the description must compensate. It adds that 'id' is a path parameter, which the schema does not specify, but it does not explain what the id identifies beyond the schema's title.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Delete Notification' and the DELETE endpoint. It clearly distinguishes itself from notification create/get/update/list tools and other delete_*_by_id sibling tools by naming the resource.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 such as update_notification_by_id or get_notification_by_id. The endpoint is shown, but no conditions, prerequisites, or exclusions are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.