Skip to main content
Glama

Rakuten items search

run_rakuten_items_search
Read-onlyIdempotent

Search live Rakuten Ichiba items by keyword with sort, condition, price range and genre filters. 1 point per returned record.

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": {
      "keyword": "<keyword>"
    },
    "name": "run_rakuten_items_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort by. Options: relevancy = Relevancy, price_low_to_high = Price: low to high, price_high_to_low = Price: high to low, newest = Newest, review_count = Most reviews, review_score = Best review score
keywordYesSearch term. e.g. コーヒー豆
genre_idNoGenre ID
conditionNoCondition. Options: new = New, used = Used
max_itemsNoMax items (up to 500) Default: 25.
price_maxNoMax price (JPY)
price_minNoMin price (JPY)
start_pageNoStarting page Default: 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so safety is covered. The description adds genuinely non-structured context: results are 'live' (real-time marketplace data) and each returned record costs '1 point', which is a billing/consumption trait the agent cannot infer from the schema or annotations.

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?

Two sentences, zero filler: capability and filters come first, the cost caveat second. Nothing is repeated from the name or title, and the billing note is placed where it will be seen before invocation.

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 an 8-parameter search tool with full schema coverage, annotations, and no output schema, the description covers purpose, filters, live-data nature, and cost. Minor gaps remain around pagination behavior (start_page/max_items interactions) and result-shape expectations, which the schema only partially conveys.

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 both enums are fully documented, so the schema carries parameter semantics. The description only lists filter categories (sort, condition, price range, genre) already visible in the schema, adding no syntax, defaults, or range detail, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Search live Rakuten Ichiba items by keyword') and enumerates the filter dimensions, so an agent can distinguish it from detail/review siblings like run_rakuten_items or run_rakuten_items_reviews. It stops short of naming those siblings explicitly, so it is clear but not fully differentiated.

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?

Usage is implied by 'by keyword with sort, condition, price range and genre filters', which tells the agent this is the keyword-search entry point for Rakuten items. There is no explicit when-to-use/when-not guidance and no pointer to alternatives such as run_rakuten_items for lookups by ID.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.