Skip to main content
Glama
arr-mcps
by arr-mcps

bookshelf_bulk_delete_importlist

Destructive

Bulk delete import lists from your Bookshelf server. Remove multiple import lists at once to clean up your configuration.

Instructions

Bulk delete importlist bulk. DESTRUCTIVE: this deletes data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNo

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 destructive hint with 'DESTRUCTIVE: this deletes data.' but adds no new behavioral context such as irreversibility, scope of deletion, or required permissions. With the annotation already declaring destructiveHint=true, this adds minimal value.

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 short but poorly structured, with the redundant 'bulk delete...bulk' phrase reducing clarity. It provides less useful information than the tool name and annotations, so it does not earn its place.

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

Completeness1/5

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

For a destructive bulk operation with an open-ended 'body' parameter, the description is severely incomplete. It does not specify what data is deleted, how to select items, or any prerequisites, leaving significant ambiguity for an agent invoking this tool.

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 schema contains a single 'body' object with additionalProperties:true and no description coverage (0%). The description does not explain what the body should contain (e.g., IDs or filters), leaving agents without any semantic guidance for constructing the request.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action (delete) and resource (importlist), but the wording 'Bulk delete importlist bulk' is redundant and awkward. It does not clearly distinguish from the sibling 'bookshelf_delete_importlist' or clarify whether it deletes multiple entries or the import list itself.

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?

No guidance is provided on when to use this bulk delete tool versus alternatives like 'bookshelf_delete_importlist' or 'bookshelf_bulk_update_importlist'. The description offers no context for tool selection.

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/arr-mcps/bookshelf-mcp'

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