Skip to main content
Glama

bookshelf_history_blocklist

Manage Bookshelf history and blocklist entries: list or delete blocklists, filter history logs, and mark failed events to trigger re-search.

Instructions

bookshelf history blocklist operations on Bookshelf. Pass operation and an arguments dict matching that operation's parameters.

  • bookshelf_bulk_delete_blocklist(body={}) — Bulk delete blocklist bulk. DESTRUCTIVE: this deletes data.

  • bookshelf_delete_blocklist(id) — Delete blocklist. DESTRUCTIVE: this deletes data.

  • bookshelf_list_blocklist(page=1, page_size=10, sort_key=None, sort_direction=None) — List blocklist. Query params: page, pageSize, sortKey, sortDirection.

  • bookshelf_list_history(page=1, page_size=10, sort_key=None, sort_direction=None, include_author=None, include_book=None, event_type=None, book_id=None, download_id=None) — List history. Query params: page, pageSize, sortKey, sortDirection, includeAuthor, includeBook, eventType, bookId, downloadId.

  • bookshelf_list_history_author(author_id=None, book_id=None, event_type=None, include_author=False, include_book=False) — List history author. Query params: authorId, bookId, eventType, includeAuthor, includeBook.

  • bookshelf_list_history_since(date=None, event_type=None, include_author=False, include_book=False) — List history since. Query params: date, eventType, includeAuthor, includeBook.

  • bookshelf_mark_history_failed(id) — Mark a history event as failed and trigger a re-search. WRITE: this modifies your Bookshelf instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentsNo
operationYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Install Server

TDQS

A3.7/5.0
Behavior4/5

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

The description explicitly flags delete operations as DESTRUCTIVE and the mark-failed operation as WRITE, informing about side effects. It does not detail all read-only operations, but the annotations are absent, so the description carries the burden effectively.

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 a structured bullet list of operations, concise and easy to scan. It avoids unnecessary verbosity, though some repetition exists in the operation summaries.

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

Completeness3/5

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

For a multi-operation tool, it provides the essential mapping of operations to parameters and flags side effects. However, it lacks information about return values or expected output formats, which may be needed for full completeness.

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 input schema is generic with only 'operation' and 'arguments', but the description enumerates each operation's parameters (e.g., page, page_size, include_author). This adds semantic detail, though individual parameter meanings are not explained.

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 clearly states that the tool handles history and blocklist operations, and lists specific operations like bulk delete, delete, list, and mark failed. It distinguishes from sibling tools by domain, though the operation descriptions are terse.

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

Usage Guidelines3/5

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

The description implies usage for history and blocklist management but does not explicitly contrast with alternative tools. There is no guidance on selecting this over others, aside from the tool's name and operation list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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

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