Skip to main content
Glama

네이버 블로그 검색

naver_openapi__blog__search

No credential or login required. 검색어(query)에 맞는 네이버 블로그 글을 찾아 목록으로 돌려줍니다. 결과 items 의 각 글에 제목(title), 글 링크(link), 요약(description), 블로그 이름(bloggername), 블로그 주소(bloggerlink), 작성일(postdate)이 있고, 전체 건수는 total 에 담깁니다. display 로 한 번에 받을 글 수(1100, 기본 10)를, start 로 시작 위치(11000, 기본 1)를, sort 로 정렬(sim 정확도순 기본, date 최신순)을 정합니다. 공개된 글만 검색되며 조회만 합니다. 별도 연동 없이 사용할 수 있습니다. For an authenticated call, generate and save request_idempotency_key before the first request. Reuse it with the same arguments only to recover that request after a lost response; use a new key for a new execution. Without it, calling again remains a new request. This optional key is not available to anonymous taste calls. Keep any provider-specific idempotency_key unchanged; it is a different field. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

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": {
      "query": "<query>"
    },
    "name": "naver_openapi__blog__search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo정렬. sim 정확도순(기본) 또는 date 최신순.
queryYes검색어.
startNo검색 시작 위치(선택, 기본 1, 최대 1000).
displayNo한 번에 받을 글 수(선택, 기본 10, 최대 100).
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

The description sends contradictory signals: '공개된 글만 검색되며 조회만 합니다' (query only) directly conflicts with the later '이 호출은 순수 읽기 전용이 아닙니다' (not purely read-only), and the former also conflicts with the readOnlyHint=false annotation. The trailing boilerplate about XBOSS tasks, per-call token consumption, and institutional data changes does not describe this search operation and reads as unrelated template text, though the idempotency-key semantics are at least concretely explained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first half is well front-loaded and efficient, but the second half is padded with generic idempotency, XBOSS, and 'institutional data change' boilerplate that is irrelevant to a public blog search and actively misleads. Roughly half the text does not earn its place.

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?

For a search tool with no output schema, the description does supply the return shape and the auth-free access model, which is adequate. But the conflicting read-only statements and the foreign boilerplate leave the agent less certain about side effects than a complete definition would, which matters given readOnlyHint=false and openWorldHint=true.

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 query, sort, start, display, and request_idempotency_key are already fully documented with ranges, defaults, and an enum. The description merely restates the display/start/sort constraints and adds no format or interaction detail beyond the schema, which is the expected baseline when the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource in its first substantive sentence: it finds Naver blog posts matching a query and returns them as a list. It goes further by enumerating the returned fields (title, link, description, bloggername, bloggerlink, postdate, total), which makes the tool unmistakable against siblings such as naver__blog__owner_post__update or the retired-API post tools.

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

Usage Guidelines3/5

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

It gives useful preconditions — no credential or login required, only publicly visible posts are searchable, and it is a query operation. However, it never states when to choose this over another search or content tool, nor any exclusion cases beyond 'public posts only', so usage is implied rather than directed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources