Skip to main content
Glama

네이버 검색광고 노출 문제 점검

naver_searchad__measurement__audit

조회만 합니다. 연동한 계정 전체(캠페인, 광고그룹, 광고, 키워드)를 읽고 광고가 나가지 못하는 이유를 알려 줍니다. 캠페인이 모두 일시정지된 경우, 광고그룹이 모두 일시정지된 경우, 비즈채널이 없는 광고그룹, 키워드와 광고가 하나도 없는 광고그룹을 찾고 항목마다 고치는 법을 함께 줍니다. 입력이 없습니다. 먼저 네이버 검색광고 계정을 연동해야 합니다. 로그인한 호출이면 첫 요청 전에 request_idempotency_key 값을 만들어 저장하세요. 응답을 받지 못한 그 요청을 되찾을 때만 같은 인자와 함께 그 값을 다시 보내고, 새로 실행할 때는 새 값을 쓰세요. 이 값 없이 다시 부르면 새 요청이 됩니다. 계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다. 기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "naver_searchad__measurement__audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 서비스에 계정을 여러 개 연동했을 때만 직접 입력해 주세요.
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / request_idempotency_key / description
      Previous value: -"Optional same-request recovery key for authenticated calls; see the tool description."New value: +"로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Given readOnlyHint=false, the description does real work: it discloses that each call consumes one token, creates an XBOSS task, and stores the processing result, and it explicitly warns that the call is not purely read-only despite the org-side lookup. The opening '조회만 합니다' sits in mild tension with that later disclaimer, and the idempotency-field aside is scaffold noise, but the net behavioral picture is consistent with the annotations rather than contradicting them.

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?

Purpose and diagnostic scope are correctly front-loaded, but the text then sprawls into organizational boilerplate about a separate org idempotency_key field and '기관 원본' policy language that an agent does not need in order to call the tool. Several of those sentences could be cut without losing invocation-relevant information.

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?

With no output schema, the description carries the return-value burden and does so by describing both what is found (the four failure patterns) and that each item comes with a remediation. Prerequisites, cost, side effects, and idempotency are all covered; only the concrete shape of the response payload is left implicit.

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 already 100%, so a baseline of 3 applies; the description earns one more by supplying the actual recovery protocol for request_idempotency_key — reuse the same value only to retry an unanswered request, use a fresh value for a new execution, and treat a call without it as a new request. The claim '입력이 없습니다' slightly understates the two optional parameters, but the idempotency guidance compensates.

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 uses a clear verb-plus-resource framing (reads the entire linked account — campaigns, adgroups, ads, keywords) and then enumerates exactly what it diagnoses: fully paused campaigns, fully paused adgroups, adgroups without a biz channel, and adgroups with no keywords or ads. That enumerated check list makes it distinguishable from the per-entity read siblings, though no sibling is named explicitly, which keeps it below a 5.

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 gives a clear operating context — use it to find out why ads are not serving — plus an explicit prerequisite (link the Naver search ad account first) and the note that no required inputs exist. What is missing is explicit routing: it never says when to prefer campaigns__read / adgroups__read / keywords__read over this account-wide audit.

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