Skip to main content
Glama
mrslbt

rakuten-mcp

by mrslbt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Rakuten Books (DVDs / Blu-ray)

books_dvd_search
Read-onlyIdempotent

Search Rakuten Books for DVDs and Blu-ray discs by title, performer, label, or JAN code. Get title details including performer, label, JAN, list price, and review stats.

Instructions

Search Rakuten Books for DVDs and Blu-ray discs by title, performer, label, or JAN (at least one; no free-text keyword, use books_total_search for that). Returns title details with performer, label, JAN, list price, and review stats.

[JA] 楽天ブックスでDVD・Blu-rayを、タイトル・出演者・レーベル・JANで検索します(いずれか必須。フリーワード検索は books_total_search)。出演者、レーベル、JAN、定価、レビューを含む詳細を返します。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
janNoJAN code. JANコード。
hitsNoNumber of results per page (1–30, default 10). 1ページあたりの取得件数(1〜30、デフォルト10)。
pageNoPage number (1+, default 1). ページ番号(1以上、デフォルト1)。
sortNoSort order. 並び順。standard
labelNoLabel/studio. レーベル/スタジオ。
titleNoTitle (movie or show). タイトル。
artistNameNoPerformer/artist. 出演者/アーティスト。
booksGenreIdNoRestrict to a specific Books genre (3-character IDs, hierarchical). Use books_genre_search to discover. ジャンルIDで絞り込み(books_genre_search で取得)。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • removedInput schema / properties / keyword
      Removed value: -{
-  "description": "Free-text keyword. キーワード。",
-  "title": "Keyword",
-  "type": "string"
-}
  2. Addedv1.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so safety is covered. The description adds the non-obvious behavioral constraint that at least one search key must be supplied and that free-text is unsupported, plus what the response contains.

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?

Two compact sentences that front-load the search scope before the exclusion, with the Japanese mirror being a convention of this catalog rather than filler. No sentence is wasted, though the bilingual duplication doubles length for monolingual readers.

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?

No output schema exists, so the description carries the return-value burden and does name the returned fields (performer, label, JAN, list price, review stats). Pagination and sort behavior are left to the schema, which is acceptable for an 8-param read-only search.

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 coverage is 100%, so per-parameter meaning is already documented (baseline 3). The description adds value the schema cannot: the cross-parameter constraint that title/performer/label/JAN must include at least one, which is invisible given required=0.

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?

States a specific verb (Search) and resource (Rakuten Books DVDs/Blu-ray), enumerates the usable keys (title, performer, label, JAN) and the return payload. It is clearly distinguishable from sibling media searches like books_cd_search or books_book_search.

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

Usage Guidelines5/5

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

Explicitly states the when-not: no free-text keyword here, route that case to books_total_search, and it names books_genre_search as the way to discover genre IDs. The 'at least one of these fields' precondition is stated outright rather than left to inference.

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

Deploy Server

Other Tools