Skip to main content
Glama

Metis ยท Librarian โ€” Remove Library Item

remove_library_item

Remove a library item from the index, with an option to delete the associated file from disk.

Instructions

Remove a library item from the Metis index, optionally deleting the file.

De-indexes a paper or document by deleting its row from library_seeded. By
default the file on disk is left untouched (index-only removal); set
delete_file=True to also delete the file, which is guarded so only paths
inside the PKM root can be removed. To hide rather than remove an item, use
archive_library_item instead.

Args:
    relative_path: The relative_path primary key identifying the row in the
        library_seeded table.
    delete_file: If True, also delete the underlying file from disk (subject
        to the within-PKM-root safety check); if False (default), only the
        index row is removed.

Returns:
    A confirmation message of what was removed, or a not-found / error
    message if the item or table is missing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
delete_fileNo
relative_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully discloses behavior: it deletes a row from library_seeded, default file left untouched, delete_file guarded to PKM root only, and returns confirmation or error. No hidden traits.

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

Conciseness5/5

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

The description is well-structured with a short summary followed by detailed Args and Returns sections. Every sentence adds value without redundancy. It is appropriately sized for the tool's complexity.

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

Completeness5/5

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

Covers return values (confirmation/error), behavior, safety mechanism, and alternative tool. Given the presence of an output schema (implied by return description), no gaps remain for a removal operation.

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

Parameters5/5

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

Schema has 0% parameter description coverage, but the description provides thorough explanations for both parameters: relative_path as primary key, delete_file with default and safety condition. This fully compensates for the schema gap.

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

Purpose5/5

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

The description clearly states it removes a library item from the Metis index with optional file deletion, and explicitly contrasts with archive_library_item for hiding. The verb 'remove' and resource 'library item' are specific and distinct from siblings.

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

Usage Guidelines5/5

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

Explicitly states when to use the alternative (archive_library_item instead of remove), and explains the two modes (index-only vs file deletion) with a safety guard. Provides clear guidance on setting delete_file.

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/SVerITG/Metis'

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