Skip to main content
Glama

archive_library_item

Archive a library item to remove it from default view while preserving it in the database for future searches and cross-pollination.

Instructions

Archive a library item (mark as no longer active but keep in DB).

Sets status='archived' in library_seeded table. Item stays available
for search and cross-pollination but disappears from default view.

Args:
    relative_path: The relative_path primary key in library_seeded table.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
relative_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses persistence (kept in DB), continued availability for search/cross-pollination, and visibility change. Lacks mention of reversibility or authorization needs, but given no annotations, provides solid behavioral context.

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?

Two focused sentences plus parameter description. No wasted words, front-loaded with purpose.

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?

Covers parameter, outcome, and behavioral changes. Could mention ability to unarchive, but output schema likely covers return values. Good for a simple tool.

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 has 1 parameter with 0% description coverage. Description adds meaning by specifying it's the primary key in library_seeded table. Could add more format details but adds value.

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?

Description clearly states verb 'archive', resource 'library item', and action (mark as no longer active, keep in DB). Distinguishes from sibling 'remove_library_item' which likely deletes.

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?

Implied usage: archive when item should be hidden from default view but remain searchable. Does not explicitly name alternatives like 'remove_library_item', but context is clear.

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