Skip to main content
Glama
mrslbt

rakuten-mcp

by mrslbt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Rakuten Books (Video Games)

books_game_search
Read-onlyIdempotent

Search Rakuten Books for video games by title, platform, or JAN code, then return hardware, label, price, and review details.

Instructions

Search Rakuten Books for video games by title, platform/hardware (e.g., 'Nintendo Switch', 'PlayStation 5'), or JAN (at least one; no free-text keyword, use books_total_search for that). Returns title details with hardware, label, JAN, list price, and review stats.

[JA] 楽天ブックスでビデオゲームを、タイトル・ハード(例: 'Nintendo Switch', 'PlayStation 5')・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
titleNoGame title. ゲームタイトル。
hardwareNoPlatform/hardware (e.g., 'Nintendo Switch'). ハードウェア(例: 'Nintendo Switch')。
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.3/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, idempotent behavior, so the safety profile is covered. The description adds value beyond that by disclosing the return payload (hardware, label, JAN, list price, review stats) in the absence of an output schema, plus the 'at least one filter' constraint that the schema does not enforce (required: 0). It stops short of mentioning pagination limits or rate limits.

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 the action, then the accepted inputs, then the exclusion and return fields in two tight sentences. The Japanese mirror doubles the length but is a deliberate, useful choice for a Japanese-market catalog tool rather than filler.

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 a 7-parameter search tool with no output schema, the description covers the return shape, the minimum-filter rule, and the discovery path for booksGenreId. Only minor gaps remain: pagination interaction between hits/page and the meaning of the sort enum are left entirely to the schema.

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 baseline is 3. The description echoes the title/hardware/JAN parameters and supplies platform examples, but those examples ('Nintendo Switch', 'PlayStation 5') already appear in the schema, and it adds nothing about hits, page, or sort semantics.

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?

Specific verb+resource ('Search Rakuten Books for video games') with the three accepted search axes named explicitly, and it explicitly names books_total_search as the sibling for the excluded free-text mode. An agent can distinguish this from books_book_search, books_software_search, and books_total_search without opening any schema.

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?

States the selection condition ('at least one' of title/hardware/JAN) and an explicit exclusion with a named alternative ('no free-text keyword, use books_total_search for that'). It also routes genre-ID discovery to books_genre_search, giving concrete when-to-use guidance for two sibling tools.

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