Skip to main content
Glama
arr-mcps

bookshelf-mcp

by arr-mcps
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

bookshelf_profiles_formats

Manage Bookshelf profiles and formats: create, fetch, update, delete, list, and reorder custom filters, custom formats, delay, metadata, quality, and release profiles via a single operation.

Instructions

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

  • bookshelf_create_customfilter(body={}) — Create customfilter. WRITE: this modifies your Bookshelf instance.

  • bookshelf_create_customformat(body={}) — Create customformat. WRITE: this modifies your Bookshelf instance.

  • bookshelf_create_delayprofile(body={}) — Create delayprofile. WRITE: this modifies your Bookshelf instance.

  • bookshelf_create_metadataprofile(body={}) — Create metadataprofile. WRITE: this modifies your Bookshelf instance.

  • bookshelf_create_qualityprofile(body={}) — Create qualityprofile. WRITE: this modifies your Bookshelf instance.

  • bookshelf_create_releaseprofile(body={}) — Create releaseprofile. WRITE: this modifies your Bookshelf instance.

  • bookshelf_delete_customfilter(id) — Delete customfilter. DESTRUCTIVE: this deletes data.

  • bookshelf_delete_customformat(id) — Delete customformat. DESTRUCTIVE: this deletes data.

  • bookshelf_delete_delayprofile(id) — Delete delayprofile. DESTRUCTIVE: this deletes data.

  • bookshelf_delete_metadataprofile(id) — Delete metadataprofile. DESTRUCTIVE: this deletes data.

  • bookshelf_delete_qualityprofile(id) — Delete qualityprofile. DESTRUCTIVE: this deletes data.

  • bookshelf_delete_releaseprofile(id) — Delete releaseprofile. DESTRUCTIVE: this deletes data.

  • bookshelf_get_customfilter(id) — Fetch a single customfilter by id.

  • bookshelf_get_customformat(id) — Fetch a single customformat by id.

  • bookshelf_get_customformat_schema() — List customformat schema.

  • bookshelf_get_delayprofile(id) — Fetch a single delayprofile by id.

  • bookshelf_get_language(id) — Fetch a single language by id.

  • bookshelf_get_metadataprofile(id) — Fetch a single metadataprofile by id.

  • bookshelf_get_metadataprofile_schema() — List metadataprofile schema.

  • bookshelf_get_qualitydefinition(id) — Fetch a single qualitydefinition by id.

  • bookshelf_get_qualityprofile(id) — Fetch a single qualityprofile by id.

  • bookshelf_get_qualityprofile_schema() — List qualityprofile schema.

  • bookshelf_get_releaseprofile(id) — Fetch a single releaseprofile by id.

  • bookshelf_list_customfilter() — List customfilter.

  • bookshelf_list_customformat() — List customformat.

  • bookshelf_list_delayprofile() — List delayprofile.

  • bookshelf_list_language() — List language.

  • bookshelf_list_metadataprofile() — List metadataprofile.

  • bookshelf_list_qualitydefinition() — List qualitydefinition.

  • bookshelf_list_qualityprofile() — List qualityprofile.

  • bookshelf_list_releaseprofile() — List releaseprofile.

  • bookshelf_reorder_delayprofile(id, after_id=None) — Update delayprofile reorder. Query params: afterId. WRITE: this modifies your Bookshelf instance.

  • bookshelf_update_customfilter(id, body={}) — Update customfilter. WRITE: this modifies your Bookshelf instance.

  • bookshelf_update_customformat(id, body={}) — Update customformat. WRITE: this modifies your Bookshelf instance.

  • bookshelf_update_delayprofile(id, body={}) — Update delayprofile. WRITE: this modifies your Bookshelf instance.

  • bookshelf_update_metadataprofile(id, body={}) — Update metadataprofile. WRITE: this modifies your Bookshelf instance.

  • bookshelf_update_quality_definitions(body=[]) — Update qualitydefinition update. WRITE: this modifies your Bookshelf instance.

  • bookshelf_update_qualitydefinition(id, body={}) — Update qualitydefinition. WRITE: this modifies your Bookshelf instance.

  • bookshelf_update_qualityprofile(id, body={}) — Update qualityprofile. WRITE: this modifies your Bookshelf instance.

  • bookshelf_update_releaseprofile(id, body={}) — Update releaseprofile. WRITE: this modifies your Bookshelf instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentsNo
operationYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Install Server

TDQS

A4.4/5.0
Behavior5/5

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

The description explicitly labels every write operation with 'WRITE: this modifies your Bookshelf instance' and delete operations with 'DESTRUCTIVE: this deletes data.' This provides clear side-effect transparency, especially important for a tool with many mutating operations, and fully compensates for the absence of annotations.

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 as a bulleted list with each operation on a single line, making it easy to scan. The opening sentence provides a concise overview, and the repetitive format is appropriate for a multi-operation tool, avoiding unnecessary verbosity while maintaining clarity.

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 all operations, their parameters, and side effects, which is adequate for the tool's scope. Since an output schema exists (as indicated by context signals), it does not need to describe return values. However, it could benefit from a brief note on common use cases or examples to enhance completeness, but this is not critical.

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?

While the input schema only defines generic `operation` and `arguments`, the description adds per-operation parameter signatures (e.g., `body={}`, `id`, `after_id`) that clarify expected arguments. It does not describe the detailed fields within `body`, but for the generic nature of the tool, this level of annotation is sufficient to guide invocation.

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's domain ('bookshelf profiles formats operations') and lists all available operations with explicit names and brief summaries. It distinguishes itself from sibling tools by focusing on profile/format management, and each operation's purpose is self-evident from its name (e.g., 'create_customfilter', 'get_qualityprofile').

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 enumerates operations but does not explicitly guide when to use this tool versus alternatives or when to choose specific operations (e.g., create vs. update). The operation names imply usage scenarios, but there is no contextual advice or decision criteria provided, leaving some ambiguity for complex cases.

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