Skip to main content
Glama

Search Rakuten Ichiba Products (Cross-Seller, with Min/Max Pricing)

ichiba_product_search
Read-onlyIdempotent

Search for a product across Rakuten shops to compare prices. Returns min, max, and average price with number of sellers for each identical product. Use to evaluate if a price is fair.

Instructions

Search Rakuten's Item Price Navi — cross-seller product catalogue that groups identical products across multiple shops. Returns each product with its min/max/average price across all sellers and the total number of shops carrying it. Use this (instead of ichiba_item_search) when you want to compare prices for a specific product or answer 'is this a fair price?'. Filter by maker_code to restrict to a brand.

[JA] 楽天市場の商品価格ナビを検索します。同一商品を複数店舗にまたがって集約し、最安値/最高値/平均価格と取扱店舗数を返します。特定商品の価格比較や「妥当な価格か?」を判断する用途では、ichiba_item_search ではなくこちらを使用してください。maker_code でブランド絞り込みも可能。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordNoProduct keyword. Required unless product_id is provided. 商品キーワード。product_id 省略時は必須。
product_idNoSpecific product ID (format like '1:12345'). When provided, returns that product. 特定の商品ID。指定時はその商品を返します。
genre_idNoRestrict results to a specific genre. ジャンルIDで絞り込み。
maker_codeNoRestrict results to a specific manufacturer (maker code). メーカーコードで絞り込み。
hitsNoNumber of results per page (1–30, default 10). 1ページあたりの取得件数。
pageNoPage number (1+, default 1). ページ番号。
sortNoSort order. '+' ascending, '-' descending. 並び順。standard
Behavior4/5

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

The description adds behavioral context beyond annotations by explaining cross-seller grouping and price aggregation. It is consistent with readOnlyHint and idempotentHint, and does not contradict any annotations. Could be improved by mentioning rate limits or response structure.

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 concise, front-loaded with English, and includes only essential information. Every sentence contributes to understanding the tool's purpose and usage.

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 search tool with 7 parameters, complete schema coverage, and safety annotations, the description provides a clear overview of functionality and use case. It explains the core aggregation and comparison capabilities, though it lacks specifics about the output format (no output schema provided).

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 does not add new meaning beyond what the schema already provides for each parameter; it only reiterates maker_code usage.

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 the tool searches Rakuten's Item Price Navi, a cross-seller catalogue that groups identical products and returns min/max/average prices across sellers. It distinguishes itself from the sibling ichiba_item_search by specifying its price comparison focus.

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?

The description explicitly says to use this tool instead of ichiba_item_search for price comparisons and fair price assessment. It also mentions filtering by maker_code, providing clear guidance on when and how to use it.

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