SiteCheck Shop & Social

Rakuten Ichiba product search from the official Rakuten Web

ecommerce_rakuten_japan

Read-only

Rakuten Ichiba (Japan) product search from the official Rakuten Web Service API: item name, price in JPY, shop, review average and count, point rate, availability, shipping flags and item link. Search results only, no stock history. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "ecommerce_rakuten_japan"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Keyword, 1 to 60 characters (Japanese or English)
`sort`	No	standard (default), +itemPrice, -itemPrice, -reviewCount, -reviewAverage, -updateTimestamp
`limit`	No	How many items, 1 to 30 (default 5)

Output Schema

Name	Required	Description	Default
`q`	No
`sort`	No
`count`	No
`items`	No
`source`	No
`checkedAt`	No
`totalHits`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses a per-call price ($0.002 USDC), the x402 payment rails, and that failed calls are not charged — critical cost and retry behavior an agent cannot infer elsewhere. It also confirms the operation is a read-only search with no history data.

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?

Two sentences, front-loaded with the capability and return fields, followed by the billing model. The field list is dense but every element earns its place; no filler wording.

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?

An output schema already exists, yet the description still summarizes the return payload and adds the payment/cost contract that structured fields do not carry. Nothing an agent needs to call this correctly is missing.

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%, with all three parameters (q, sort, limit) documented including defaults and sort options, so the description adds no parameter meaning on top of the schema. 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 ('Rakuten Ichiba (Japan) product search from the official Rakuten Web Service API') and enumerates the returned fields, so the agent knows exactly what this tool produces. The scoping statement 'Search results only, no stock history' further bounds the purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage (search the Japanese Rakuten marketplace) and gives one exclusion ('no stock history'), but never says when to pick this over the numerous sibling marketplace tools such as ecommerce_amazon_bestsellers or ecommerce_aliexpress. Guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SiteCheck Shop & Social tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?