Skip to main content
Glama
yukincom

rakuten-pantry-mcp

by yukincom

Search Rakuten Ichiba Products

ichiba_item_search
Read-onlyIdempotent

Search Rakuten Ichiba products by keyword with price range, sorting, and genre/shop filters. Returns prices, reviews, images, and shipping-verified total cost.

Instructions

Search products on Rakuten Ichiba (Japan's largest e-commerce marketplace) by keyword. Supports price range filtering, sorting by review count/average/price, and restricting results to a specific genre or shop. Returns items with prices, review stats, images, purchase URLs, quantity, unitPrice, postageLabel (from postageFlag), estimatedTotalPrice, and shippingVerified. For cheapest / per-unit / shipping-inclusive comparisons (送料込み, コスパ, 安い順, 最安): use the compare_ichiba_value PROMPT instead of this tool alone. If you must use this tool directly: (1) pre-sort by unitPrice ascending; (2) shippingVerified=true → estimatedTotalPrice is final; (3) web-search top 3–5 shippingVerified=false items for JPY shipping; (4) re-rank by itemPrice+shipping; never guess shipping.

[JA] 楽天市場で商品をキーワード検索します。各商品にquantity・unitPrice・postageLabel・estimatedTotalPrice・shippingVerifiedを付与します。送料込み・コスパ・安い順・最安の比較は compare_ichiba_value プロンプトを使うこと(このツール単体は不十分)。直接使う場合: (1) unitPrice昇順 (2) shippingVerified=trueは確定 (3) false上位3〜5件をウェブ検索 (4) 再ソート。送料推測禁止。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsNoNumber of results to return per page (1–30, default 10). 1ページあたりの取得件数(1〜30、デフォルト10)。
pageNoPage number (1+, default 1). ページ番号(1以上、デフォルト1)。
sortNoSort order. Prefix '+' = ascending, '-' = descending. 並び順。'+' は昇順、'-' は降順。standard
keywordYesSearch keyword. Accepts Japanese or English. 検索キーワード。日本語または英語。
genre_idNoRestrict to a specific genre ID. Browse genres via ichiba_genre_search. ジャンルIDで絞り込み。
max_priceNoMaximum price in JPY (integer, inclusive). 最高価格(円、整数、以下)。
min_priceNoMinimum price in JPY (integer, inclusive). 最低価格(円、整数、以上)。
shop_codeNoRestrict to a specific shop. 特定の店舗で絞り込み。
Behavior4/5

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

Annotations already declare readOnly and idempotent. The description adds value by detailing the shipping verification logic and the derived fields (postageLabel, estimatedTotalPrice), but does not mention any behavioral edge cases beyond that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is bilingual with full Japanese translation, making it longer than necessary. While front-loaded with purpose, the repetition reduces conciseness. Could be trimmed to essential English.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description fully explains return fields and shipping logic. It covers usage guidelines, alternatives, and parameter summary, making it complete for the tool's complexity.

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 coverage is 100%, so the description adds little new meaning to parameters. It summarizes available filters but doesn't provide additional context beyond what the schema already describes.

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?

Clearly states 'Search products on Rakuten Ichiba by keyword' with specific verb and resource. Lists supported filters and return fields, distinguishing it from sibling tools like genre_search or ranking.

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 tells when to use an alternative (compare_ichiba_value for value comparisons) and provides step-by-step instructions if used directly, including sorting, shipping verification, and prohibitions on guessing shipping.

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/yukincom/rakuten-pantry-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server