XBOSS

네이버 검색광고 광고 만들기

naver_searchad__ads__create

Destructive

광고그룹에 광고 하나를 만듭니다. nccAdgroupId, type, ad(그 유형의 소재)를 넣고, RSA_AD 이면 assets(제목과 설명)도 넣습니다. 광고는 네이버 심사를 거친 뒤 노출됩니다. 소재는 나중에 고칠 수 없으므로, 바꾸려면 새 광고를 만들고 옛 광고를 일시정지하거나 지우세요. 먼저 네이버 검색광고 계정을 연동해야 합니다. This writes to the institution. The first call is not executed: it returns a preview of exactly what will be sent and a one-time confirmation_token (error WRITE_CONFIRMATION_REQUIRED). Show that preview to the user as it is. Only after the user agrees, call again with the same arguments plus that confirmation_token. Never add the token without the user's agreement. Changing any argument makes the token invalid; call without the token to get a new preview. 호출마다 토큰 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": {
      "nccAdgroupId": "<nccAdgroupId>",
      "type": "<type>",
      "ad": "<ad>"
    },
    "name": "naver_searchad__ads__create"
  }
}

Input Schema

Name	Required	Description
`ad`	Yes	그 광고 유형의 소재.
`type`	Yes	광고 유형(예: TEXT_45, RSA_AD).
`adAttr`	No	선택. 그 광고 유형의 광고 속성.
`assets`	No	RSA_AD 의 제목과 설명. 수가 모자라면 네이버가 거절합니다.
`nccAdgroupId`	Yes	광고그룹 id(nccAdgroupId). 광고그룹 목록 조회 결과에서 얻습니다.
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 서비스에 계정을 여러 개 연동했을 때만 직접 입력해 주세요.
`confirmation_token`	No	첫 호출이 돌려준 1회용 확인 토큰입니다(오류 WRITE_CONFIRMATION_REQUIRED). 같은 인자에 이 값을 그대로 넣어 다시 호출하면 실행됩니다. 10분 뒤 만료되고 한 번만 쓸 수 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Well beyond the annotations, it discloses the two-phase write flow (first call is a dry-run preview returning WRITE_CONFIRMATION_REQUIRED plus a one-time token, second call with the same args plus token executes), token expiry at 10 minutes, single use, invalidation on any argument change, that each call consumes a token and spawns an XBOSS job, and that the ad goes through Naver review before serving. The destructive/immutability trait is explicitly stated ('소재는 나중에 고칠 수 없으므로').

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 confirmation-flow explanation is front-loaded and earned, but the trailing block repeats itself across languages ('This writes to the institution' and then the Korean sentence saying the call is not purely read-only), and the XBOSS/job bookkeeping sentence is administrative noise for the calling agent. Roughly a third of the text could be cut without losing decision-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?

For a 7-parameter nested-object mutation with no output schema, it covers prerequisites, the confirmation handshake, mutation irreversibility, and async review. The main omission is what the successful call returns (e.g. the created ad id) and what to do on review rejection, but the confirmation behavior is fully specified.

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 the baseline is 3; the description earns above that by explaining the conditional relationship between type=RSA_AD and assets (titles and descriptions), and warning that an insufficient number of assets will be rejected by Naver. It does not clarify adAttr or account_link_id semantics, which remain schema-only.

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 opening sentence gives a specific verb and resource ('광고그룹에 광고 하나를 만듭니다') that clearly separates it from the sibling adgroups/campaigns/keywords create tools by resource. It also names the required inputs (nccAdgroupId, type, ad) and the RSA_AD special case, though it never explicitly names a sibling to contrast against.

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 real when-to-use context: a Naver Search Ad account must be linked first, and RSA_AD requires assets. It also gives when-not/alternative guidance — '소재는 나중에 고칠 수 없으므로, 바꾸려면 새 광고를 만들고 옛 광고를 일시정지하거나 지우세요' — steering the agent toward create+pause/delete rather than an edit path. It stops short of naming the ads__update or ads__delete siblings explicitly.

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?