Skip to main content
Glama

Search Rakuten Books (Printed Books)

books_book_search
Read-onlyIdempotent

Find printed books on Rakuten by title, author, ISBN, publisher, or keyword. Retrieves details like ISBN, price, author, and review statistics.

Instructions

Search Rakuten Books for printed books by title, author, ISBN, publisher, or free-text keyword. Returns book details including ISBN, author, publisher, series, table of contents, preview URL, list price, and review stats. Pass at least one search field.

[JA] 楽天ブックスで紙の書籍を、書名・著者・ISBN・出版社・キーワードで検索します。ISBN、著者、出版社、シリーズ、目次、立ち読みURL、定価、レビューを含む書籍詳細を返します。検索条件は少なくとも1つ必須。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoBook title (partial match). 書名(部分一致)。
authorNoAuthor name. 著者名。
publisherNameNoPublisher name. 出版社。
isbnjanNoISBN or JAN code. ISBN または JAN コード。
keywordNoFree-text keyword across all fields. 全フィールド横断のキーワード。
hitsNoNumber of results per page (1–30, default 10). 1ページあたりの取得件数(1〜30、デフォルト10)。
pageNoPage number (1+, default 1). ページ番号(1以上、デフォルト1)。
sortNoSort order. 並び順。standard
booksGenreIdNoRestrict to a specific Books genre (3-character IDs, hierarchical). Use books_genre_search to discover. ジャンルIDで絞り込み(books_genre_search で取得)。
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint. The description adds valuable behavioral details: returns book details including ISBN, author, publisher, series, table of contents, preview URL, list price, and review stats. No contradictions with 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 two concise English sentences (plus Japanese translation) with zero wasted words. It front-loads the purpose and key details.

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?

Given high schema coverage and clear annotations, the description is complete: it lists return fields, requires at least one search parameter, and defines scope. No output schema exists, so the description adequately covers return value expectations.

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 description coverage is 100%, but the description adds the constraint that at least one search field must be provided, which is not in the schema. It also summarizes the search fields, though the schema already describes each parameter.

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 it searches for printed books by title, author, ISBN, publisher, or keyword, distinguishing it from sibling tools for CDs, DVDs, ebooks, etc. It specifies 'printed books' explicitly, differentiating from kobo_ebook_search.

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?

The description includes the critical guideline to 'Pass at least one search field.' It implies when to use via context (printed books vs. other media), but lacks explicit exclusions or alternative tool mentions.

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/mrslbt/rakuten-mcp'

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