Skip to main content
Glama

remove_library_item

Remove an indexed library item and optionally delete its file from disk.

Instructions

Remove a library item from the Metis index.

Deletes the row from library_seeded. If delete_file=True, also deletes
the actual file from disk (only if path is within PKM root — safety check required).

Args:
    relative_path: The relative_path primary key in library_seeded table.
    delete_file: If True, also delete the file from disk. Default False.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
relative_pathYes
delete_fileNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description carries the full burden. It discloses the deletion of a row and a safety check for file deletion, but does not specify if the operation is destructive, reversible, or requires permissions. The 'safety check required' is vague.

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 concise with a clear summary followed by parameter details. Every sentence is informative with no wasted words. The 'Args:' section is well-structured.

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?

Given an output schema exists, the description adequately covers input behavior. It explains main action, safety check, and parameter effects. Could mention error handling or return value, but not critically missing.

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?

The description explains both parameters beyond the schema: relative_path as primary key and delete_file controlling file deletion with a safety check. Schema coverage is 0%, so description adds necessary meaning.

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 states 'Remove a library item from the Metis index' and explains the deletion of a row and optional file removal. The verb and resource are specific, but it does not explicitly distinguish from siblings like 'archive_library_item' or 'remove_project'.

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 on when to use this tool versus alternatives. It mentions conditions for delete_file but no when-not-to-use or comparisons with other tools.

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