Skip to main content
Glama
isnow890

Naver Search MCP Server

datalab_shopping_by_device

Analyze shopping trends on Naver by device type (PC or mobile) to identify user behavior patterns and optimize marketing strategies over specific time periods.

Instructions

Perform a trend analysis on Naver Shopping by device. (네이버 쇼핑 기기별 트렌드 분석)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYesCategory code
deviceYesDevice type
endDateYesEnd date (yyyy-mm-dd)
startDateYesStart date (yyyy-mm-dd)
timeUnitYesTime unit

Implementation Reference

  • Handler function that takes DatalabShoppingDevice parameters, maps them, and delegates to the NaverSearchClient's datalabShoppingByDevice method to fetch shopping trends by device.
    /**
     * 쇼핑 기기별 트렌드 핸들러
     * 네이버 데이터랩 쇼핑 기기별 트렌드 분석 API 호출
     * @param params DatalabShoppingDevice
     */
    export async function handleShoppingByDeviceTrend(
      params: DatalabShoppingDevice
    ) {
      return client.datalabShoppingByDevice({
        startDate: params.startDate,
        endDate: params.endDate,
        timeUnit: params.timeUnit,
        category: params.category,
        device: params.device,
      });
    }
  • Zod input schema for the datalab_shopping_by_device tool, extending base schema with category code and device (pc/mo).
    export const DatalabShoppingDeviceSchema = DatalabBaseSchema.extend({
      category: z.string().describe("Category code"),
      device: z.enum(["pc", "mo"]).describe("Device type"),
    });
  • src/index.ts:298-317 (registration)
    MCP server registration of the 'datalab_shopping_by_device' tool, specifying description, input schema (subset of DatalabShoppingDeviceSchema), and async handler that calls datalabToolHandlers and formats response.
    server.registerTool(
      "datalab_shopping_by_device",
      {
        description:
          "📱 Analyze shopping trends by device (PC vs Mobile). Use find_category first. BUSINESS CASES: Mobile commerce strategy, responsive design priority, device-specific campaigns. EXAMPLE: 'PC 사용자가 더 많이 구매하는 카테고리는?' For current device trends, use get_current_korean_time to set proper analysis period. (기기별 쇼핑 트렌드 분석 - 먼저 find_category 도구로 카테고리 코드를 찾고, 현재 기기 트렌드 분석시 get_current_korean_time으로 적절한 분석 기간 설정)",
        inputSchema: DatalabShoppingDeviceSchema.pick({
          startDate: true,
          endDate: true,
          timeUnit: true,
          category: true,
          device: true,
        }).shape,
      },
      async (args) => {
        const result = await datalabToolHandlers.datalab_shopping_by_device(args);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      }
    );
  • NaverSearchClient method that performs the HTTP POST request to Naver DataLab API endpoint for shopping category trends by device.
     */
    async datalabShoppingByDevice(
      params: DatalabShoppingDeviceRequest
    ): Promise<DatalabShoppingResponse> {
      return this.post(`${this.datalabBaseUrl}/shopping/category/device`, params);
    }
  • Internal handler map registration in datalabToolHandlers object that logs args and calls the specific handleShoppingByDeviceTrend function.
    datalab_shopping_by_device: (args) => {
      console.error("datalab_shopping_by_device called with args:", JSON.stringify(args, null, 2));
      return handleShoppingByDeviceTrend(args);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'trend analysis' but doesn't specify what that entails (e.g., returns data, charts, insights), whether it's read-only or has side effects, or any constraints like rate limits or authentication needs. This is inadequate for a tool with 5 required parameters.

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 brief and front-loaded with the core purpose. The Korean translation adds redundancy but doesn't significantly detract. It could be more concise by omitting the translation, but it's still efficient with no wasted sentences.

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 tool with 5 required parameters, no annotations, and no output schema, the description is incomplete. It lacks behavioral context (e.g., what the analysis returns, any limitations), usage guidance relative to siblings, and doesn't compensate for the absence of structured metadata. This leaves significant gaps for an agent.

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 the schema already documents all parameters thoroughly. The description adds no parameter-specific information beyond implying device analysis, which is covered by the 'device' parameter's enum. Baseline 3 is appropriate when the schema does the heavy lifting.

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 tool performs 'trend analysis on Naver Shopping by device' with a Korean translation. It specifies the verb ('perform trend analysis'), resource ('Naver Shopping'), and scope ('by device'), but doesn't explicitly differentiate from sibling tools like 'datalab_shopping_by_age' or 'datalab_shopping_by_gender' beyond the device focus.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention sibling tools like 'datalab_shopping_by_age' or 'datalab_shopping_by_gender' for comparison, nor does it specify prerequisites or exclusions. The description only states what it does, not when it's appropriate.

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