Skip to main content
Glama
korea-data-mcp

korea-data-mcp

by parkseokjune

oliveyoung_rankings

Fetch Olive Young K-beauty bestseller rankings and product data as clean English JSON; search by keyword or category and set item limits and sort order.

Instructions

Return Olive Young (Korea's #1 health & beauty retailer) K-beauty bestseller rankings and products as clean English JSON. Olive Young has ZERO dedicated competitor on Apify.

Args: mode: One of "ranking", "search", or "category". query: Search keyword or category id (used when mode is "search" or "category"). Empty applies actor default. maxItems: Maximum number of products to return. sort: Sort order, e.g. "MOST_POPULAR".

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": "oliveyoung_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoranking
sortNoMOST_POPULAR
queryNo
maxItemsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It mentions clean English JSON output and that an empty query applies the actor default, but it omits operational details such as data freshness, pagination, rate limits, and authentication requirements.

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 purpose is front-loaded and the Args section is easy to scan. However, the marketing sentence about having ZERO dedicated competitor on Apify does not help an agent select or invoke the tool and slightly weakens conciseness.

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

Completeness3/5

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

The description covers the tool's purpose, all parameters, and output format, and an output schema exists to explain return values. It still lacks guidance on sibling alternatives and operational behavior, which matters because no annotations are supplied.

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

Parameters4/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 it does document all four parameters. It explains mode values, query usage for search/category, maxItems meaning, and gives a sort example, though it does not enumerate all valid sort values or category id formats.

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 Olive Young K-beauty bestseller rankings and products as English JSON. It is clear what the tool does, but it does not explicitly differentiate itself from sibling ranking tools such as glowpick_rankings or musinsa_rankings.

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 explains the mode values and when query is used, which implies usage contexts for ranking, search, and category modes. However, it gives no explicit guidance on when to choose this tool over sibling alternatives or when not to use it.

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