XBOSS

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

naver_searchad__performance__report

Read-only

Read-only. Returns impressions, clicks and cost for campaigns or ad groups over a date range. Pass the entity id, the fields to report, and a datePreset such as last7days. Connect the Naver Search Ad account first. 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소진

Input Schema

Name	Required	Description
`id`	Yes	The campaign or ad group id to report on.
`fields`	Yes	Metrics to return, e.g. ["impCnt","clkCnt","salesAmt"].
`datePreset`	Yes	Reporting window, e.g. last7days, last30days.
`output_formats`	No	Optional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.
`account_link_id`	No	Account link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple connections for the same provider.
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / request_idempotency_key

Added value: +{
+  "description": "Optional same-request recovery key for authenticated calls; see the tool description.",
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[\\x20-\\x7E]+$",
+  "type": "string"
+}

Changed1 schema field changedOct 26, 2026

changedInput schema / properties / account_link_id / description

Previous value: -"Account link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple certificates for the same provider. Each institution has a separate ID (Hometax != NHIS != NPS != FourInsure)."New value: +"Account link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple connections for the same provider."

Changed1 schema field changedOct 15, 2026

addedInput schema / properties / output_formats

Added value: +{
+  "description": "Optional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.",
+  "items": {
+    "enum": [
+      "xlsx"
+    ],
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}

AddedOct 12, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Beyond the readOnly/destructive annotations, the description discloses token consumption per call, artifact/download retention windows, expired-link recovery through xdata__job__result, anonymous recovery_receipt handling, and request_idempotency_key lifecycle rules. This is substantial operational context that the annotations do not provide.

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?

The purpose and required inputs are front-loaded, but the description is overstuffed with anonymous-access receipt details, references to 'taste calls' and 'lane', and a trailing untranslated Korean token-cost note. Many sentences are useful, but several are tangential or confusing for this specific tool.

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 six-parameter reporting tool with artifact output but no output schema, the description covers the key context: account connection, metrics, date presets, file artifacts, retention, recovery, and idempotency. It could still be clearer about the exact result shape beyond artifacts[].

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 description coverage is 100%, so the baseline is already strong. The description still adds useful meaning for output_formats (xlsx only when requested) and especially for request_idempotency_key reuse/recovery semantics, though it does not cover every parameter.

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 gives a specific verb and resource: it returns impressions, clicks, and cost for campaigns or ad groups over a date range. This distinguishes it semantically from metadata-read siblings like campaigns__read/adgroups__read, though no sibling is named explicitly.

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 the prerequisite to connect the Naver Search Ad account first and how to pass required inputs, but it does not explicitly say when to use this performance report instead of the related read tools or list exclusions. Usage is implied by the stated metrics rather than fully guided.

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

All XBOSS tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?