Skip to main content
Glama
mrslbt

rakuten-mcp

by mrslbt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Rakuten Ichiba Bestseller Ranking

ichiba_item_ranking
Read-onlyIdempotent

Retrieve Rakuten Ichiba realtime bestseller rankings overall or filtered by genre, age, or gender. Returns ranked items with price and review stats for market research.

Instructions

Get the Rakuten Ichiba realtime bestseller ranking: overall, for one genre, or for an age/gender demographic. Genre and demographic filters are mutually exclusive (Rakuten restriction). Returns ranked items with their rank, price, review stats, and purchase URL. Use ichiba_genre_search to find genre IDs.

[JA] 楽天市場のリアルタイム売れ筋ランキングを取得します。総合、ジャンル別、または年代/性別で絞り込み可能。ジャンルと年代/性別は併用できません(楽天の仕様)。順位、価格、レビュー、購入URLを含むランキング一覧を返します。ジャンルIDの検索には ichiba_genre_search を使用してください。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageNoFilter to an age demographic. '50s' means 50 and over. Overall ranking only (genre_id must be '0'). 年代フィルタ。'50s' は50代以上。総合ランキングのみ(genre_id は '0')。
sexNoFilter to a gender demographic. Overall ranking only (genre_id must be '0'). 性別フィルタ。総合ランキングのみ(genre_id は '0')。
pageNoPage number (1–34; Rakuten caps rankings at ~1000 items). ページ番号(1〜34)。
genre_idNoGenre ID for the ranking. '0' returns the overall ranking. Cannot be combined with age or sex (Rakuten restriction). 0はジャンル全体のランキング。age/sex とは併用不可(楽天の仕様)。0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.3.0
    • changedInput schema / properties / age / description
      Previous value: -"Filter to a specific age demographic (e.g., '20s' = users in their 20s). 年代フィルタ。"New value: +"Filter to an age demographic. '50s' means 50 and over. Overall ranking only (genre_id must be '0'). 年代フィルタ。'50s' は50代以上。総合ランキングのみ(genre_id は '0')。"
    • changedInput schema / properties / age / enum
      Previous value: -[
-  "10s",
-  "20s",
-  "30s",
-  "40s",
-  "50s",
-  "60s",
-  "70s"
-]New value: +[
+  "10s",
+  "20s",
+  "30s",
+  "40s",
+  "50s"
+]
    • changedInput schema / properties / genre_id / description
      Previous value: -"Genre ID for the ranking. '0' returns the overall ranking. 0はジャンル全体のランキング。"New value: +"Genre ID for the ranking. '0' returns the overall ranking. Cannot be combined with age or sex (Rakuten restriction). 0はジャンル全体のランキング。age/sex とは併用不可(楽天の仕様)。"
    • removedInput schema / properties / period
      Removed value: -{
-  "description": "Time window for the ranking. Default depends on Rakuten's current configuration. ランキングの集計期間。",
-  "enum": [
-    "realtime",
-    "daily",
-    "weekly",
-    "monthly",
-    "yearly"
-  ],
-  "title": "Period",
-  "type": "string"
-}
    • changedInput schema / properties / sex / description
      Previous value: -"Filter to a specific gender demographic. 性別フィルタ。"New value: +"Filter to a gender demographic. Overall ranking only (genre_id must be '0'). 性別フィルタ。総合ランキングのみ(genre_id は '0')。"
  2. Addedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered. The description adds real value beyond that: the Rakuten-imposed mutual exclusion between genre and age/sex filters, and the shape of the payload (rank, price, review stats, purchase URL) in the absence of an output schema.

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 purpose, then constraints, then routing hint, then return contents — a sensible order with no filler. The only cost is the complete Japanese duplication of the same content, which doubles length without adding information for a single-language consumer.

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 4-parameter, all-optional read tool with no output schema, the description covers the ranking modes, the key cross-parameter constraint, and the returned fields. What is missing is only marginal — e.g. how the 1–34 page cap interacts with the ~1000-item ceiling, which the schema already states.

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% and each parameter (age, sex, page, genre_id) is already documented in-schema with enums, defaults, and range limits. The description restates the genre/age/sex exclusivity that the schema already carries, adding no syntax or format detail beyond it. Baseline 3 applies.

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 ('Get the Rakuten Ichiba realtime bestseller ranking') and immediately enumerates the three supported scoping modes (overall, genre, demographic). It also names the sibling ichiba_genre_search as the way to obtain genre IDs, so an agent can distinguish it from the other ichiba_* tools without opening schemas.

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 clear operating context: the three ranking modes, the mutually exclusive genre vs. demographic rule, and a routing hint to ichiba_genre_search for genre IDs. It does not, however, say when to prefer this ranking tool over ichiba_item_search or ichiba_product_search, so the alternative-selection guidance is incomplete.

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