Skip to main content
Glama
Naver Search MCP Server

Naver Search MCP Server

by neneungyul2

datalab_shopping_keyword_by_gender

Analyze shopping keyword trends by gender within a category to guide targeted marketing and product positioning. Use find_category first to get category codes.

Instructions

๐Ÿ‘ฅ๐Ÿ” Analyze keyword performance by gender within shopping categories. Use find_category first to get category codes. Essential for gender-targeted marketing and product positioning strategies. (์‡ผํ•‘ ํ‚ค์›Œ๋“œ ์„ฑ๋ณ„ ํŠธ๋ Œ๋“œ - ๋จผ์ € find_category ๋„๊ตฌ๋กœ ์นดํ…Œ๊ณ ๋ฆฌ ์ฝ”๋“œ๋ฅผ ์ฐพ์œผ์„ธ์š”)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "startDate": "<startDate>",
      "endDate": "<endDate>",
      "timeUnit": "<timeUnit>",
      "category": "<category>",
      "keyword": "<keyword>",
      "gender": "<gender>"
    },
    "name": "datalab_shopping_keyword_by_gender"
  }
}

Input Schema

NameRequiredDescriptionDefault
genderYesGender
endDateYesEnd date (yyyy-mm-dd or 'today' for KST today)
keywordYesSearch keyword
categoryYesCategory code
timeUnitYesTime unit
startDateYesStart date (yyyy-mm-dd or 'today' for KST today)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the two-step dependency on find_category, but says nothing about the operation being a read-only analytics query, the shape or granularity of the returned metrics, or any rate/quota limits. The prerequisite is real added value; the rest of the behavioral profile is absent.

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 English portion is tight and front-loaded, but the parenthetical Korean sentence is a near-verbatim duplicate of the first two English sentences, which is pure waste. The emoji prefix also adds no selecting signal.

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?

Six required parameters, no output schema, and no annotations make this a moderately complex tool. The description covers purpose and one prerequisite but never indicates what the response contains (e.g. a time series of keyword metrics split by gender), which an agent would need to interpret 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 all six parameters are documented structurally. The description adds only one piece of semantic value beyond the schema: that the 'category' code must come from find_category. Date format, timeUnit granularity, and gender enum meaning are left entirely to the schema.

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?

States a specific verb and resource: 'Analyze keyword performance by gender within shopping categories.' That clearly separates it from the category-level sibling datalab_shopping_by_gender, though the description never names that sibling explicitly. An agent can infer the distinction from the 'keyword' vs 'category' framing, but it isn't spelled out.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete prerequisite ordering ('Use find_category first to get category codes') and a use case ('gender-targeted marketing and product positioning'). It does not state when to prefer this over datalab_shopping_keyword_by_age or datalab_shopping_keyword_by_device, but the context is clear enough to act on.

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