Skip to main content
Glama
leadbrain

korean-data-mcp

get_musinsa_ranking

Fetch Musinsa fashion ranking data by category to track Korea's trends. Choose category slug (e.g., outer, top) and limit items up to 100.

Instructions

Fetch Musinsa (무신사) fashion ranking — Korea's leading fashion platform.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoCategory slug, e.g. 'all', 'outer', 'top', 'bottom', 'shoes', 'bag'all
max_itemsNoMaximum number of items to return (default 50, max 100)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_musinsa_ranking' tool. Fetches Musinsa (무신사) fashion ranking data by calling the Apify actor 'oxygenated_quagmire/musinsa-ranking-scraper' with a category slug and max_items limit.
    async def get_musinsa_ranking(
        category: str = "all",
        max_items: int = 50,
    ) -> list[dict]:
        """
        Fetch Musinsa (무신사) fashion ranking — Korea's leading fashion platform.
    
        Args:
            category: Category slug, e.g. 'all', 'outer', 'top', 'bottom', 'shoes', 'bag'
            max_items: Maximum number of items to return (default 50, max 100)
    
        Returns:
            List of product objects with rank, name, brand, price, discountRate, url fields.
        """
        max_items = min(max_items, 100)
        return await _run_actor(
            f"{APIFY_ACCOUNT}/musinsa-ranking-scraper",
            {"category": category, "maxItems": max_items},
        )
  • The @mcp.tool() decorator registers the function as an MCP tool on the FastMCP server instance.
    @mcp.tool()
  • The _run_actor helper function used by get_musinsa_ranking to execute the Apify actor and return dataset items.
    async def _run_actor(actor_id: str, input_data: dict, timeout_secs: int = 60) -> list[dict]:
        """Run an Apify actor synchronously and return dataset items."""
        token = _get_token()
        url = f"{APIFY_BASE}/acts/{actor_id}/run-sync-get-dataset-items"
        params = {"token": token}
    
        async with httpx.AsyncClient(timeout=timeout_secs + 10) as client:
            resp = await client.post(url, json=input_data, params=params)
            resp.raise_for_status()
            return resp.json()
  • Input schema: category (string, default 'all') and max_items (int, default 50, max 100). Output schema: list[dict] with rank, name, brand, price, discountRate, url fields.
        category: str = "all",
        max_items: int = 50,
    ) -> list[dict]:
Behavior2/5

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

No annotations are provided, so the description must disclose behaviors like rate limits, data freshness, or authentication needs. It only states 'fetch ranking' without any such details, leaving the agent unaware of potential constraints.

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?

The description is a single, efficient sentence with no wasted words. It front-loads the key purpose and provides enough context for a simple fetch tool.

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?

Given the output schema exists and the tool is straightforward, the description is largely complete. However, briefly mentioning the category or max_items parameters could enhance completeness.

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?

The input schema has 100% coverage with clear parameter descriptions. The description adds no extra meaning beyond the schema, so a baseline score of 3 is appropriate.

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?

The description clearly states the verb 'Fetch' and the resource 'Musinsa fashion ranking', immediately conveying the tool's function. It differentiates well from sibling tools which target other platforms like Melon or Naver.

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 for fetching Musinsa ranking but provides no explicit guidance on when to use it versus alternatives, nor any context about prerequisites or typical use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/leadbrain/korean-data-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server