XBOSS

네이버 검색광고 캠페인 목록 조회

naver_searchad__campaigns__read

조회만 합니다. 연동한 네이버 검색광고 계정의 캠페인 목록을 돌려줍니다. 캠페인마다 id, 이름, 유형, 상태가 들어 있습니다. 먼저 네이버 검색광고 계정을 연동해야 합니다. 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

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__campaigns__read"
  }
}

Input Schema

Name	Required	Description
`output_formats`	No	선택 입력입니다. 결과를 엑셀(xlsx) 파일로도 받으려면 입력해 주세요. 파일은 결과의 artifacts[] 에 실립니다. 비워 두면 데이터만 받습니다.
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 서비스에 계정을 여러 개 연동했을 때만 직접 입력해 주세요.
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.5/5.0

Behavior4/5

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

The description discloses genuine behavior beyond the annotations: it creates XBOSS jobs, stores results, and explicitly warns this is not purely read-only despite the 'read' name — consistent with readOnlyHint=false. It also covers artifact retention (7-day file retention, 15-minute download links), recovery_receipt semantics, and idempotency-key reuse rules. The opening '조회만 합니다' is mildly at odds with the later '순수 읽기 전용이 아닙니다' and slightly muddies the signal.

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?

A large share of the text is cross-cutting boilerplate about anonymous receipts, publishing, signing up, and file retention that is largely irrelevant to listing campaigns, and it is interleaved Korean and English with no structure. The most important disclosure — that this is not a pure read — is buried in the final clause rather than front-loaded.

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?

Coverage is broad: return fields, prerequisites, artifacts, retention, and idempotency are all present, which is good given there is no output schema. But the leading '조회만 합니다' contradicts the later 'not purely read-only' statement, and the noise makes it hard for an agent to extract what actually governs correct invocation.

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 baseline would be 3; the description earns a 4 by supplying the actual operational semantics for request_idempotency_key (generate before first request, reuse only to recover a lost response, new key per new execution) that the schema only gestures at. output_formats timing and the anonymous-call restriction are also clarified.

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 first two sentences state a specific verb and resource: '연동한 네이버 검색광고 계정의 캠페인 목록을 돌려줍니다' and enumerate the returned fields (id, 이름, 유형, 상태). An agent can tell this lists campaigns rather than adgroups/ads/keywords. It does not explicitly contrast with those sibling reads, keeping it from 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 Guidelines3/5

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

It states one real prerequisite ('먼저 네이버 검색광고 계정을 연동해야 합니다'), which is useful, and mentions when to supply output_formats. However, it never says when to use this versus sibling read tools or how to scope by account when multiple are linked; usage is only implied by the resource name.

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?