Skip to main content
Glama
SavageCore
by SavageCore

bookshelf_delete_importlist

Destructive

Deletes an import list from Bookshelf using its ID. This destructive action permanently removes the list and its configuration, so use only when you intend to remove the import source.

Instructions

Delete importlist. 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 phrase 'DESTRUCTIVE: this deletes data' merely restates the existing annotation destructiveHint=true. It adds no new behavioral context such as permanence, cascading effects, or authorization requirements. With annotations already covering destructiveness, this is redundant.

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 concise and front-loaded with the core action. However, the second phrase 'DESTRUCTIVE: this deletes data' is redundant with the annotation, though it does not add significant verbosity. Overall, it is minimal but not wordy.

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 single-parameter delete operation, the description is incomplete. It fails to explain the meaning of the required 'id' field or any side effects beyond the annotation. Since the output schema exists, return values are not needed, but the input semantics are critically underserved.

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 description does not mention the 'id' parameter at all. With schema description coverage at 0%, the description entirely fails to explain that 'id' is the identifier of the importlist to delete. This leaves the agent without critical information for correct invocation.

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 'Delete importlist' clearly states the action (delete) and the resource (importlist). While it doesn't explicitly distinguish from bulk_delete_importlist, the singular resource and parameter 'id' imply it targets a single importlist. The purpose is unambiguous.

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?

The description gives no guidance on when to use this tool versus alternatives. It does not mention bulk operations, prerequisites, or that this tool is for deleting a specific importlist by ID. No exclusions or alternative tool references are provided.

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

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