Skip to main content
Glama
isnow890

Naver Search MCP Server

search_shop

Search for products on Naver Shopping by entering a query, sorting results by relevance or date, and customizing the number and start position of displayed results for targeted shopping inquiries.

Instructions

Perform a search on Naver Shopping. (네이버 쇼핑 검색)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
displayNoNumber of results to display (default: 10)
queryYesSearch query
sortNoSort method (sim: similarity, date: date)
startNoStart position of search results (default: 1)

Implementation Reference

  • Core handler function that executes the shop search using NaverSearchClient.search('shop', params). This is the primary implementation of the tool logic.
    /**
     * 쇼핑 검색 핸들러
     */
    export async function handleShopSearch(params: SearchArgs) {
      return client.search("shop", params);
    }
  • Dispatcher function in searchToolHandlers that logs args, validates with schema, and delegates to handleShopSearch.
    search_shop: (args) => {
      console.error("search_shop called with args:", JSON.stringify(args, null, 2));
      return handleShopSearch(SearchArgsSchema.parse(args));
    },
  • src/index.ts:147-160 (registration)
    MCP server registration of the 'search_shop' tool, including description, input schema reference, and handler invocation.
    server.registerTool(
      "search_shop",
      {
        description:
          "🛒 Search Naver Shopping for products, prices, and shopping deals. Compare prices across vendors, find product specifications, and discover shopping trends in Korea. For current deals or today's specials, use get_current_korean_time first. (네이버 쇼핑 검색 - 상품 정보와 가격 비교, 현재 할인이나 오늘 특가를 찾을 때는 먼저 get_current_korean_time으로 현재 시간을 확인하세요)",
        inputSchema: SearchArgsSchema.shape,
      },
      async (args) => {
        const result = await searchToolHandlers.search_shop(args);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      }
    );
  • Zod schema defining the input parameters for search tools, including query, display, start, and sort options. Used for validation in search_shop.
    export const SearchArgsSchema = z.object({
      query: z.string().describe("검색어"),
      display: z.number().optional().describe("한 번에 가져올 결과 수 (기본 10)"),
      start: z.number().optional().describe("검색 시작 위치 (기본 1)"),
      sort: z
        .enum(["sim", "date"])
        .optional()
        .describe("정렬 방식 (sim: 유사도, date: 날짜순)"),
    });
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 'Perform a search' but lacks behavioral details like rate limits, authentication requirements, pagination behavior, error handling, or what the search results look like. For a search tool with zero annotation coverage, this is a significant gap in transparency.

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 extremely concise with just one sentence plus a parenthetical translation, front-loading the core purpose without any wasted words. Every element serves a clear purpose, making it efficient and well-structured.

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?

Given no annotations and no output schema, the description is incomplete for a search tool. It doesn't explain what the tool returns (e.g., result format, fields), behavioral constraints, or how it differs from sibling tools. The high schema coverage helps with parameters, but overall context is lacking for effective agent use.

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 fully documents all 4 parameters (query, display, sort, start) with descriptions and defaults. The description adds no additional parameter semantics beyond what's in the schema, meeting the baseline of 3 for high schema coverage.

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 search') and target resource ('Naver Shopping'), with the Korean translation adding specificity. However, it doesn't differentiate from sibling tools like search_blog or search_news that perform similar search operations on different platforms, missing explicit 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?

No guidance is provided on when to use this tool versus alternatives. With many sibling tools for different search types (e.g., search_blog, search_news, search_webkr), the description offers no context about appropriate use cases or exclusions, leaving the agent to infer based on tool names alone.

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