Skip to main content
Glama
korea-data-mcp

korea-data-mcp

by parkseokjune

naver_shopping_best

Retrieve Naver Shopping bestseller rankings as clean English JSON by specifying ranking mode, category ID, and item limit for market research and product trend analysis.

Instructions

Return Naver Shopping bestseller rankings as clean English JSON.

Args: mode: Ranking mode, e.g. "buy". categoryId: Category id, e.g. "A". maxItems: Maximum number of items to return.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "naver_shopping_best"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNobuy
maxItemsNo
categoryIdNoA

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It conveys one useful trait — results are localized into clean English JSON — but says nothing about pagination, item caps, rate limits, category validity, or what happens when categoryId is unrecognized.

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?

The core purpose is front-loaded in one sentence, followed by a compact args list. Wording is efficient, with only mild redundancy between the arg labels and the schema titles.

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

Completeness2/5

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

An output schema exists, so return shape need not be described, but for a three-parameter tool with zero schema documentation and no annotations, the definition is thin. The unenumerated mode and categoryId values are the main omission an agent would need filled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and largely does not. It restates the three field names with opaque examples ("buy", "A") but never enumerates valid modes or category ids, leaving the agent unable to select a value with confidence.

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?

The description states a specific verb and resource: return Naver Shopping bestseller rankings. Naming the source marketplace distinguishes it from sibling price/ranking tools such as danawa_prices or musinsa_rankings, though it never explicitly contrasts behavior with them.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The only hints are inline examples of parameter values, which describe arguments rather than usage conditions.

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