Skip to main content
Glama

Builderlog

키워드 월 검색량

blog_keyword_volume
Read-only

키워드 최대 5개(로그인 없이 3개)의 네이버 월 검색량(PC·모바일)을 알려요. 최근 7일 안에 잰 값이 있으면 그 값을 쓰고, 블로그 팩 이용권이 있는 로그인 회원은 없는 값을 네이버 검색광고 키워드 도구에서 새로 가져와요(하루 한도 있음). 내 네이버 검색광고 키를 붙인 로그인 회원은 그 키로 새로 가져오고, 그 값은 보관하지 않아요(붙이는 법: builderlog_setup). 순위·문서 수·검색 추이는 알려 주지 않고, 키워드와 검색량만 7일 보관하며 어떤 키워드를 누가 물었는지는 남기지 않아요.

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": {
      "keywords": "<keywords>"
    },
    "name": "blog_keyword_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYes검색량을 알고 싶은 키워드(최대 5개, 각 20자 안)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses caching (values measured within 7 days are reused), the external data source (Naver Search Ad keyword tool), a daily fetch limit, and that values fetched with a user-supplied key are not persisted. It also states retention (7 days for keyword+volume) and that no per-user query log is kept, which is exactly the kind of privacy and side-effect context annotations cannot express.

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 definition is front-loaded with what the tool returns, then layers on caching, quota, key handling, and exclusions in dependency order; every clause carries operational information. It is dense but not padded, though the multi-clause sentences make it slightly harder to scan than a bulleted structure would.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter lookup with no output schema, the description covers the source of the numbers, the caching window, and the PC/mobile breakdown, so an agent knows what comes back in substance. The exact response shape (e.g., how missing volumes are represented) is left implicit, which is the only remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents the single keywords array, its 5-item cap, and the 20-character limit. The description adds meaning the schema lacks, namely that the effective count is 3 when unauthenticated versus 5 when logged in, which changes how an agent should populate the array.

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 (returns Naver monthly search volume, PC and mobile, for up to 5 keywords) and explicitly bounds the scope by saying rank, document count, and search trends are not returned. An agent can distinguish this from sibling analysis tools like blog_check or blog_decay_check without opening the schema.

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?

It lays out concrete preconditions and tiers: up to 3 keywords without login, 5 when logged in, fresh fetches require a blog pack pass or the user's own Naver Search Ad key, and there is a daily quota. It even routes to builderlog_setup for attaching a key. The only gap is that it does not name an alternative tool for the rank/trend questions it declines.

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