Skip to main content
Glama
mrslbt

rakuten-mcp

by mrslbt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Rakuten Books (Magazines)

books_magazine_search
Read-onlyIdempotent

Search Rakuten Books for magazines by title, publisher, or JAN to retrieve issue details including publisher, JAN, publication cycle, preview URL, and review stats.

Instructions

Search Rakuten Books for magazines by title, publisher, or JAN (at least one; no free-text keyword, use books_total_search for that). Returns issue details including publisher, JAN, publication cycle, preview URL, and review stats.

[JA] 楽天ブックスで雑誌を、タイトル・出版社・JANで検索します(いずれか必須。フリーワード検索は books_total_search)。出版社、JAN、発行サイクル、立ち読みURL、レビューを含む詳細を返します。

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
titleNoMagazine title. 雑誌名。
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, openWorldHint and idempotentHint, so the safety profile is covered. The description adds the non-obvious constraint that at least one of title/publisher/JAN is required (the schema encodes required: 0), which is real behavioral value, and it lists what the response contains. It omits rate limits and any note on what an empty result set means.

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 sentence is front-loaded with purpose and the exclusion, then the return payload, and the Japanese mirror is an intentional bilingual duplicate rather than padding. The return-detail enumeration (publisher, JAN, publication cycle, preview URL, review stats) is slightly long but earns its place given there is no output schema.

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 7 optional parameters, no output schema, and full schema coverage, the description supplies the two things structured data lacks: the at-least-one-field requirement and the shape of the returned issue details. It does not explain pagination limits or how genre IDs interact with title filters, leaving minor gaps for a search tool of this complexity.

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%, so the baseline is 3 and the schema already explains hits, page, sort and the genre-ID format. The description goes beyond that by imposing the 'at least one of title/publisher/JAN' rule that the schema does not express, which is genuine added meaning for a zero-required-parameter tool.

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 and resource (search Rakuten Books for magazines) plus the three accepted filter fields, and explicitly distinguishes itself from books_total_search by excluding free-text keyword search. An agent can separate this from the many sibling book/media searches (books_book_search, books_cd_search, kobo_ebook_search) 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?

Gives a clear routing rule: no free-text keyword here, use books_total_search for that, and it names books_genre_search (in the schema) as the way to discover genre IDs. It does not spell out when magazine search is the wrong choice versus, say, kobo_ebook_search or books_book_search, so it stops short of full when/when-not guidance.

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