Skip to main content
Glama
mrslbt

rakuten-mcp

by mrslbt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Rakuten Books (CDs / Music)

books_cd_search
Read-onlyIdempotent

Search Rakuten Books for music CDs by title, artist, label, or JAN code and return album details, track lists, pricing, and review stats.

Instructions

Search Rakuten Books for music CDs by title, artist, label, or JAN code (at least one; no free-text keyword, use books_total_search for that). Returns album/single details including artist, label, JAN, track list, list price, and review stats.

[JA] 楽天ブックスで音楽CDを、タイトル・アーティスト・レーベル・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
labelNoRecord label. レーベル。
titleNoAlbum/single title. アルバム/シングル名。
artistNameNoArtist name. アーティスト名。
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 readOnlyHint/openWorldHint/idempotentHint, so safety is covered. The description adds value beyond them by enumerating what is returned (artist, label, JAN, track list, list price, review stats), which helps the agent anticipate payload without an output schema. It does not mention pagination behavior or rate limits, so it is not complete.

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 single paragraph: purpose first, constraint second, return payload third. Every sentence carries information. The parallel Japanese translation doubles the length but is an intentional bilingual convention rather than padding, keeping it shy of 5.

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 filtered search tool this covers what an agent needs: queryable fields, the required-one constraint, the sibling to use for free text, and return contents. No output schema exists, yet return fields are described, and pagination is handled by well-documented hits/page params. Only minor gaps remain.

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 baseline is 3. The description earns above baseline by surfacing the 'at least one of title/artist/label/JAN' constraint, which the schema does not enforce (0 required params), and by surfacing that no free-text keyword is accepted. It does not elaborate on sort enum or genre-id semantics, which remain schema-only.

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 music CDs) with the searchable facets named (title, artist, label, JAN). It also differentiates from siblings: which sibling is not appropriate ('no free-text keyword, use books_total_search') and implicitly from books_book_search/books_dvd_search by scoping to CDs/music. An agent can distinguish this from the other ~27 siblings without opening a schema.

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?

Explicitly states a usage precondition (at least one of title/artist/label/JAN) and names the alternative for free-text (books_total_search). This is clear context with an exclusion. It stops short of routing among the other near-identical media search siblings (books_book_search, books_dvd_search), so it is not a full 5.

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