Skip to main content
Glama
isnow890

Naver Search MCP Server

search_blog

Search Naver Blog posts by query, specify result count, sort by relevance or date, and define start position for precise results.

Instructions

Perform a search on Naver Blog. (네이버 블로그 검색)

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

  • The main handler function for 'search_blog' tool. Logs the args and delegates to handleBlogSearch after schema validation.
    search_blog: (args) => {
      console.error("search_blog called with args:", JSON.stringify(args, null, 2));
      return handleBlogSearch(SearchArgsSchema.parse(args));
  • Helper function that performs the actual Naver blog search using the client.
    /**
     * 블로그 검색 핸들러
     */
    export async function handleBlogSearch(params: SearchArgs) {
      return client.search("blog", params);
  • Zod schema for input validation of search tools, including search_blog.
    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: 날짜순)"),
    });
  • src/index.ts:132-145 (registration)
    MCP server registration of the 'search_blog' tool, including description and input schema reference.
    server.registerTool(
      "search_blog",
      {
        description:
          "✍️ Search personal blogs and reviews for authentic user experiences. Great for product reviews, personal stories, detailed tutorials, and real user opinions. Find genuine Korean perspectives. For recent posts or 'today's content', use get_current_korean_time first. (네이버 블로그 검색 - 실제 사용자 후기와 개인적 경험, 최근 글이나 오늘 내용을 찾을 때는 먼저 get_current_korean_time으로 현재 시간을 확인하세요)",
        inputSchema: SearchArgsSchema.shape,
      },
      async (args) => {
        const result = await searchToolHandlers.search_blog(args);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      }
    );
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 states the basic action but doesn't describe what the search returns (blog posts, metadata, links), whether there are rate limits, authentication requirements, or how results are structured. For a search tool with no annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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 two short phrases that convey the essential purpose. Both the English and Korean versions are front-loaded with the core functionality, and there's no wasted language or unnecessary elaboration.

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 search tool with no annotations and no output schema, the description is insufficient. It doesn't explain what kind of results to expect (blog posts, metadata, links), how results are formatted, or any limitations. The combination of missing behavioral context and lack of output information makes this description incomplete for effective tool 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 already documents all 4 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema. The baseline of 3 is appropriate when the schema does all the parameter documentation work.

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 ('on Naver Blog'), with the Korean translation adding clarity for the specific platform. However, it doesn't distinguish this from sibling tools like search_news or search_webkr, which also perform searches on Naver platforms but for different content types.

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 about when to use this tool versus alternatives. The description doesn't mention what makes blog search unique compared to other search tools in the sibling list, nor does it specify prerequisites or typical use cases for blog content versus other content types.

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