Skip to main content
Glama
mrslbt

rakuten-mcp

by mrslbt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Rakuten Books (Foreign-Language Books)

books_foreign_book_search
Read-onlyIdempotent

Search Rakuten Books for foreign-language books by title, author, ISBN, or publisher. Get book details and Japanese-translated titles when available.

Instructions

Search Rakuten Books for foreign-language (non-Japanese) books by title, author, ISBN, or publisher (at least one; no free-text keyword, use books_total_search for that). Returns book details plus a Japanese-translated title field when available.

[JA] 楽天ブックスで洋書を、タイトル・著者・ISBN・出版社で検索します(いずれか必須。フリーワード検索は books_total_search)。書籍詳細に加え、邦題が存在する場合は japaneseTitle を返します。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsNoNumber of results per page (1–30, default 10). 1ページあたりの取得件数(1〜30、デフォルト10)。
isbnNoISBN. ISBN。
pageNoPage number (1+, default 1). ページ番号(1以上、デフォルト1)。
sortNoSort order. 並び順。standard
titleNoTitle (English or other). タイトル。
authorNoAuthor. 著者。
booksGenreIdNoRestrict to a specific Books genre (3-character IDs, hierarchical). Use books_genre_search to discover. ジャンルIDで絞り込み(books_genre_search で取得)。
publisherNameNoPublisher. 出版社。

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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds two useful pieces of context not present in structured fields: the mandatory at-least-one-field rule (which is stricter than the schema's required: 0) and the return content, including a Japanese-translated title field when one exists. It stops short of describing pagination limits, though the schema covers those.

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 English text is two tight sentences with the scope and the sibling exclusion front-loaded. The bilingual duplication doubles the length, but it mirrors the schema's own bilingual field descriptions and does not bury the operative constraint.

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?

For an eight-parameter read-only search with no output schema, the definition covers purpose, the required-input rule, the alternative tool, and the notable return field (japaneseTitle). Pagination and sort semantics live in the schema, so nothing essential is missing, though the description never states what a result set looks like structurally.

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 all eight parameters are already documented with their bounds, defaults, and the enum for sort. The description only restates which fields can be searched (title/author/ISBN/publisher) and omits any detail on hits, page, sort, or booksGenreId. Baseline 3 is correct when the schema carries the parameter burden.

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 a precisely scoped resource: foreign-language (non-Japanese) books in Rakuten Books, searchable by title, author, ISBN, or publisher. The non-Japanese scope cleanly separates it from books_book_search, and the explicit hand-off to books_total_search separates it from that sibling.

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 usage constraint ('at least one' of the four search fields) and names the exclusion plus the alternative for the excluded case: 'no free-text keyword, use books_total_search for that'. An agent can route between this tool and its sibling without any 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