Skip to main content
Glama
isnow890

Naver Search MCP Server

datalab_shopping_category

Analyze Naver Shopping category trends by specifying time units, date ranges, and category codes to identify market patterns and consumer behavior.

Instructions

Perform a trend analysis on Naver Shopping category. (네이버 쇼핑 카테고리별 트렌드 분석)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYesArray of category name and code pairs
endDateYesEnd date (yyyy-mm-dd)
startDateYesStart date (yyyy-mm-dd)
timeUnitYesTime unit

Implementation Reference

  • Handler function that executes the core logic by delegating to the Naver client for shopping category trend analysis.
    export async function handleShoppingCategoryTrend(params: DatalabShopping) {
      return client.datalabShoppingCategory(params);
    }
  • Zod schema defining the input parameters for the datalab_shopping_category tool, including category details.
    // 쇼핑 카테고리 스키마
    export const DatalabShoppingSchema = DatalabBaseSchema.extend({
      category: z
        .array(
          z.object({
            name: z.string().describe("Category name"),
            param: z.array(z.string()).describe("Category codes"),
          })
        )
        .describe("Array of category name and code pairs"),
    });
  • src/index.ts:283-296 (registration)
    MCP server tool registration for datalab_shopping_category, including description and input schema reference.
    server.registerTool(
      "datalab_shopping_category",
      {
        description:
          "🛍️ STEP 2: Analyze shopping category trends over time. Use find_category first to get category codes. BUSINESS CASES: Market size analysis, seasonal trend identification, category performance comparison. EXAMPLE: Compare '패션의류' vs '화장품' trends over 6 months. For current period analysis, use get_current_korean_time to set proper date ranges. (네이버 쇼핑 카테고리별 트렌드 분석 - 먼저 find_category 도구로 카테고리 코드를 찾고, 현재 기간 분석시 get_current_korean_time으로 적절한 날짜 범위 설정)",
        inputSchema: DatalabShoppingSchema.shape,
      },
      async (args) => {
        const result = await datalabToolHandlers.datalab_shopping_category(args);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      }
    );
  • Client method that performs the actual HTTP POST request to Naver DataLab API for shopping categories.
    async datalabShoppingCategory(
      params: DatalabShoppingCategoryRequest
    ): Promise<DatalabShoppingResponse> {
      return this.post(`${this.datalabBaseUrl}/shopping/categories`, params);
  • Handler map entry that logs args and delegates to the specific trend handler.
    datalab_shopping_category: (args) => {
      console.error("datalab_shopping_category called with args:", JSON.stringify(args, null, 2));
      return handleShoppingCategoryTrend(args);
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'trend analysis' but doesn't disclose what this entails operationally - whether it's a read-only query, requires authentication, has rate limits, returns aggregated data, or what format the analysis takes. The Korean translation adds no behavioral information.

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 description is appropriately brief with two equivalent language versions. However, the Korean translation adds no new information and could be considered redundant. The core English statement is front-loaded and efficient.

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?

For a data analysis tool with 4 required parameters and no output schema, the description is insufficient. It doesn't explain what 'trend analysis' returns, what metrics are analyzed, or provide context about the Naver Shopping platform. Without annotations or output schema, users must guess about the tool's behavior and results.

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%, so parameters are well-documented in the schema. The description doesn't add any meaningful parameter semantics beyond what's already in the schema - it doesn't explain how categories relate to trend analysis, what the time unit affects, or provide examples of valid category inputs.

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 clearly states the action ('Perform a trend analysis') and target resource ('Naver Shopping category'), making the purpose understandable. It distinguishes from some siblings like 'datalab_shopping_by_age' by specifying category-level analysis, though it doesn't explicitly differentiate from all similar tools like 'datalab_shopping_keywords'.

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?

The description provides no guidance on when to use this tool versus alternatives. With multiple sibling tools for shopping data analysis (e.g., by age, device, gender, keywords), there's no indication of when category trend analysis is preferred over other dimensions or keyword analysis.

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

Related 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/isnow890/naver-search-mcp'

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