Skip to main content
Glama
mrslbt

rakuten-mcp

by mrslbt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Rakuten Books (Printed Books)

books_book_search
Read-onlyIdempotent

Search Rakuten Books for printed books by title, author, ISBN, publisher, or genre to retrieve book details including ISBN, author, publisher, series, contents, preview URL, price, and reviews.

Instructions

Search Rakuten Books for printed books by title, author, ISBN, publisher, or genre (at least one; no free-text keyword, use books_total_search for that). Returns book details including ISBN, author, publisher, series, table of contents, preview URL, list price, and review stats.

[JA] 楽天ブックスで紙の書籍を、書名・著者・ISBN・出版社・ジャンルで検索します(いずれか必須。フリーワード検索は books_total_search)。ISBN、著者、出版社、シリーズ、目次、立ち読みURL、定価、レビューを含む書籍詳細を返します。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsNoNumber of results per page (1–30, default 10). 1ページあたりの取得件数(1〜30、デフォルト10)。
isbnNoISBN code, digits only (e.g. 9784815630614). ISBNコード(ハイフンなし)。
pageNoPage number (1+, default 1). ページ番号(1以上、デフォルト1)。
sortNoSort order. 並び順。standard
titleNoBook title (partial match). 書名(部分一致)。
authorNoAuthor name. 著者名。
booksGenreIdNoRestrict to a specific Books genre (3-character IDs, hierarchical). Use books_genre_search to discover. ジャンルIDで絞り込み(books_genre_search で取得)。
publisherNameNoPublisher name. 出版社。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.0
    • addedInput schema / properties / isbn
      Added value: +{
+  "description": "ISBN code, digits only (e.g. 9784815630614). ISBNコード(ハイフンなし)。",
+  "title": "ISBN",
+  "type": "string"
+}
    • removedInput schema / properties / isbnjan
      Removed value: -{
-  "description": "ISBN or JAN code. ISBN または JAN コード。",
-  "title": "Isbnjan",
-  "type": "string"
-}
    • removedInput schema / properties / keyword
      Removed value: -{
-  "description": "Free-text keyword across all fields. 全フィールド横断のキーワード。",
-  "title": "Keyword",
-  "type": "string"
-}
  2. Addedv1.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description adds genuinely useful context beyond them: the mandatory-at-least-one-parameter constraint and the shape of the returned payload (ISBN, author, publisher, series, TOC, preview URL, price, review stats), which matters because there is no output schema.

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?

Front-loaded with purpose, then constraint, then return payload; every sentence carries information. The bilingual duplication doubles the length, which is defensible for a Japanese-market API but is still redundancy from a token-efficiency standpoint.

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?

With no output schema, the description compensates by enumerating the returned fields, and it covers the invocation precondition. Minor gap: no mention of pagination interaction between hits/page beyond what the schema states, and no note on empty-result behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter is already documented in the schema, including the enum for sort and the 1–30 / 1–100 bounds. The description restates the searchable fields and the no-free-text rule but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 printed books) plus the exact search axes (title, author, ISBN, publisher, genre). It also explicitly distinguishes itself from books_total_search for free-text and from the other format-specific siblings (CD/DVD/magazine/foreign) by scoping to printed books.

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?

Gives an explicit precondition ('at least one' of the listed fields) and an explicit exclusion with the alternative ('no free-text keyword, use books_total_search for that'). The genre parameter also points at books_genre_search for discovery, so routing decisions need no 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