Skip to main content
Glama

LeoWorks Data Tools — Naver, K-beauty & AliExpress

leoworks/kbeauty-ranking-review-monitor

leoworks--kbeauty-ranking-review-monitor
Destructive

This tool calls the Actor "leoworks/kbeauty-ranking-review-monitor" and retrieves its output results. Actor description: Track K-beauty bestseller rankings on Olive Young Global (OliveYoung, 올리브영) and Amorepacific's Amore Mall (아모레몰: Sulwhasoo, Laneige, Hera…) and collect cosmetics reviews with optional AI classification — complaint types, sentiment and purchase motive in Korean, English and Japanese. No login.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandsNoOptional. Keep only products of these brands (English or Korean name, e.g. COSRX, 설화수). The whole ranking (up to 100) is searched and the original rank is kept.
sourcesNoWhich bestseller rankings to collect. Leave empty to only collect reviews for the product pages below. Example values: ["oliveyoung_global"]
waitSecsNoMax seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
reviewSortNoAmore Mall supports Newest and Most helpful; other orders fall back to Newest there. Example values: "newest"newest
healthCheckNoInternal: fail the run when results look degraded (used by the developer's scheduled checks).
productUrlsNoOptional. Olive Young Global or Amore Mall product pages to collect reviews for, in addition to the ranked products.
maxConcurrencyNoRankings and products processed in parallel. Example values: 5
amoremallPeriodNoRanking period on Amore Mall. Example values: "daily"daily
classifyReviewsNoAdd complaint types, sentiment and purchase motive to each Korean, English or Japanese review (charged per review as review-judged). Example values: true
rankHistoryStoreNoName of a key-value store in your Apify account that keeps the last snapshot of each ranking. Ranking rows then show `previousRank`, `rankChange` (positive = moved up) and `isNew` (not in the previous ranking). Run on a schedule to track movement. Use a different name per project; leave empty to turn this off. No extra charge. Example values: "kbeauty-ranking-history"kbeauty-ranking-history
amoremallAgeGroupNoBuyer age group for the Amore Mall ranking. Example values: "all"all
amoremallRankingsNoAmore Mall ranking tabs to collect. Example values: ["best_purchased"]
reviewsPerProductNoReviews to collect for each product (0 = rankings only). Charged per review. The form starts at 5 for a quick first run; raise it up to 1,000 (default when omitted via API: 20). Example values: 5
complaintThresholdNoMinimum probability (0–1) for a complaint type to be reported. Example values: 0.5
proxyConfigurationNoDefault Apify datacenter proxy works for both sites. Example values: {"useApifyProxy":true}
amoremallCategoriesNoAmore Mall categories (one ranking per category and ranking type). Example values: ["all"]
residentialFallbackNoRetry failing requests through Korean residential proxy. Example values: true
oliveyoungCategoriesNoBestseller tabs to collect (one ranking per category). Example values: ["all"]
includeProductDetailsNoAdd each Olive Young Global ranking product's information sheet as `productDetails`: full ingredient list, volume, skin type it is made for, country of manufacture, manufacturer, plus all other sheet fields. One extra request per product; no extra charge. Amore Mall rows are not covered.
maxProductsPerRankingNoTop N products of each ranking (rankings have up to 100 products). Each product row is charged as ranking-item. The form starts at 5 for a quick first run; raise it up to 100 (default when omitted via API: 20). Example values: 5

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tipNoAdvisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key
runIdYesActor run ID
statsNoRun statistics
statusYesRun status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED
actorIdYesStable Apify Actor ID from the run record
summaryYesPast-tense summary of the run state
exitCodeNoActor process exit code; populated for terminal states (especially FAILED)
nextStepYesOne primary follow-up action with identifiers interpolated
storagesYesDataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
actorNameNo"username/actor-name"
startedAtNoISO timestamp when the run started
finishedAtNoISO timestamp when the run finished (terminal states only)
statusMessageNoPass-through from Apify run.statusMessage
apifyConsoleUrlNoPersonalized Apify Console link to the run; present only for Console sessions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, lowering the disclosure bar. The description adds the useful behavioral fact that no login is required, but it does not explain the run lifecycle, the per-review/per-ranking-item charging that the schema mentions, or why the operation is destructive.

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 tight sentences that front-load the actor identity and then the capability summary; no padding. Slightly boilerplate in the first clause ('This tool calls the Actor ... and retrieves its output results'), but nothing wasteful.

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?

An output schema exists, so return values need not be described, and the 20-parameter schema is fully documented. The description covers sources, review collection and AI classification adequately, though it omits the asynchronous run/polling behavior that an agent needs for long runs.

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% across all 20 parameters, so the schema fully documents names, enums, defaults and trade-offs like cost and proxy behavior. The description adds no parameter meaning of its own, so the baseline of 3 is appropriate.

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 gives a concrete verb+resource: tracking K-beauty bestseller rankings on Olive Young Global and Amore Mall and collecting reviews with optional AI classification. That is specific and understandable. It does not, however, differentiate itself from siblings such as leoworks--naver-shopping-rank-tracker or leoworks--korean-review-classifier, so an agent must infer the distinction.

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 when-to-use guidance, no mention of when not to use it, and no reference to any alternative tool. The 'No login' note is a fact about the actor, not usage guidance. The agent gets no help choosing between this and the other ranking/review siblings.

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.