Skip to main content
Glama

remove_library_item

Remove a library item from the Metis index. Optionally delete the file from disk, with safety checks to ensure only files inside the PKM root can be removed.

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
relative_pathYes
delete_fileNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that by default only the index is removed, file deletion is guarded to paths within PKM root, and returns confirmation or error messages. It does not detail permissions, but the safety guard is mentioned.

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 well-structured with a brief summary followed by details on behavior, parameters, and returns. It is front-loaded and clear, though could be slightly more concise without losing information.

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

Completeness4/5

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

The description covers purpose, parameters, behavioral details, safety, and return value. Given that an output schema exists (context signal), the return description suffices. For a 2-parameter tool with no annotations, it is fairly complete.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. It explains both parameters: 'relative_path' as primary key, and 'delete_file' with default False and safety check. This adds meaning beyond the schema, though the format of relative_path is not specified.

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 the tool removes a library item from the Metis index, optionally deleting the file. It uses a specific verb 'remove' and resource 'library item', and distinguishes itself from the sibling tool 'archive_library_item' which hides rather than removes.

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

Usage Guidelines4/5

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

The description provides guidance on when to use this tool versus 'archive_library_item' (hide instead of remove), and explains the optional file deletion. However, it does not explicitly state when not to use it (e.g., for items that shouldn't be removed).

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_PH'

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