Skip to main content
Glama

네이버 검색광고 성과 보고서 조회

naver_searchad__performance__report

조회만 합니다. 캠페인이나 광고그룹 하나의, 정한 기간 동안의 노출수, 클릭수, 비용을 돌려줍니다. id(캠페인이나 광고그룹의 id), fields(보고할 지표), datePreset(기간, 예: last7days)을 넣습니다. 먼저 네이버 검색광고 계정을 연동해야 합니다. Files: a document generated from this result, as Excel (xlsx) only when requested in output_formats, listed in artifacts[] of the result with a download_url that works for 15 minutes; each file is kept for 7 days. If a link has expired, call xdata__job__result with the job_id from the result for fresh links. For an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane. 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": {
      "id": "<id>",
      "fields": "<fields>",
      "datePreset": "<datePreset>"
    },
    "name": "naver_searchad__performance__report"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe campaign or ad group id to report on.
fieldsYesMetrics to return, e.g. ["impCnt","clkCnt","salesAmt"].
datePresetYesReporting window, e.g. last7days, last30days.
output_formatsNo선택 입력입니다. 결과를 엑셀(xlsx) 파일로도 받으려면 입력해 주세요. 파일은 결과의 artifacts[] 에 실립니다. 비워 두면 데이터만 받습니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 서비스에 계정을 여러 개 연동했을 때만 직접 입력해 주세요.
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

A3.5/5.0
Behavior4/5

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

Well beyond the annotations, it discloses that the call creates an XBOSS job, stores the result, consumes one token per call, and is not purely read-only — which is consistent with readOnlyHint=false. It also explains the artifact lifecycle (xlsx only when output_formats requests it, download_url valid 15 minutes, files kept 7 days) and the recovery path via xdata__job__result. It loses a point for the internal tension between "조회만 합니다" and "순수 읽기 전용이 아닙니다", and for not saying what the job creation means for the caller.

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 text is heavily padded with generic platform boilerplate about recovery receipts, idempotency keys, and file retention that is only partly specific to this tool, and it switches between Korean and English mid-paragraph. The single most operationally important caveat — that this call is not purely read-only — is buried in the final sentences instead of being front-loaded.

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?

There is no output schema, yet the description covers the return payload (metrics), the optional artifact output and its URL lifetime, the account-linking prerequisite, token cost, and idempotency handling. What remains unclear is whether the stored XBOSS job has any downstream effect an agent must account for.

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 coverage is 100%, so the schema already documents all six parameters, including output_formats, account_link_id, and request_idempotency_key. The description only restates id, fields, and datePreset and adds the example "last7days", which the schema also provides; it adds no new semantics for the optional parameters.

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?

"캠페인이나 광고그룹 하나의, 정한 기간 동안의 노출수, 클릭수, 비용을 돌려줍니다" names the verb, the resource, the grain (one campaign or ad group), and the returned metrics, so an agent can distinguish it from the sibling read tools. However, the opening "조회만 합니다" (read only) is undercut by the later "이 호출은 순수 읽기 전용이 아닙니다" (not purely read-only), leaving the tool's actual nature mildly ambiguous at first read.

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 states one prerequisite clearly: the Naver Search Ad account must be linked first. It gives no guidance on when to pick this over the sibling report tools (google__ads__* reports, google__analytics__report) or over naver_searchad__campaigns__read for entity data, and no exclusion conditions.

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