XBOSS

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

naver_searchad__adgroups__create

Destructive

캠페인 아래에 광고그룹 하나를 만듭니다. nccCampaignId, name, adgroupType 과 PC 와 모바일의 비즈채널 id(pcChannelId, mobileChannelId)를 넣습니다. 비즈채널 id 는 기존 광고그룹 목록 조회 결과에 있고, 광고그룹이 하나도 없으면 네이버 검색광고 관리 화면에서 비즈채널을 확인하도록 안내하세요. 새 광고그룹도 일시정지 상태로 만들어지고 자체 하루 예산 한도가 없습니다. 하루 예산을 정한 뒤 켜도록 안내하세요. 입찰가와 하루 예산은 아직 이 도구로 정하거나 바꿀 수 없습니다. bidAmt, dailyBudget, budget 을 넣은 요청은 거절되므로 네이버 검색광고 관리 화면에서 정하도록 안내하세요. 먼저 네이버 검색광고 계정을 연동해야 합니다. 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": {
      "nccCampaignId": "<nccCampaignId>",
      "name": "<name>",
      "adgroupType": "<adgroupType>",
      "pcChannelId": "<pcChannelId>",
      "mobileChannelId": "<mobileChannelId>"
    },
    "name": "naver_searchad__adgroups__create"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	광고그룹 이름.
`adgroupType`	Yes	광고그룹 유형. 보통 캠페인 유형과 같습니다(예: WEB_SITE).
`pcChannelId`	Yes	PC 에서 쓰는 비즈채널 id.
`nccCampaignId`	Yes	캠페인 id(nccCampaignId). 캠페인 목록 조회 결과에서 얻습니다.
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 서비스에 계정을 여러 개 연동했을 때만 직접 입력해 주세요.
`mobileChannelId`	Yes	모바일에서 쓰는 비즈채널 id.
`confirmation_token`	No	첫 호출이 돌려준 1회용 확인 토큰입니다(오류 WRITE_CONFIRMATION_REQUIRED). 같은 인자에 이 값을 그대로 넣어 다시 호출하면 실행됩니다. 10분 뒤 만료되고 한 번만 쓸 수 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Well beyond the annotations, it discloses the created resource's state (paused, no own daily budget limit), the two-phase write protocol (first call returns a preview plus a one-time confirmation_token under WRITE_CONFIRMATION_REQUIRED, token expires in 10 minutes, changing arguments invalidates it, never attach it without user consent), and the side effect of creating an XBOSS job per call. This is exactly the behavioral context an agent needs before invoking a mutating tool.

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 operation and required fields are front-loaded, but the text is bloated by repetition — the 'guide them to the Naver admin screen' instruction appears twice — and by trailing boilerplate about XBOSS jobs and institutional originals that adds little for the caller. Language also switches between Korean and English mid-paragraph, which fragments the read.

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 write tool with no output schema, the definition covers prerequisites, side effects, rejected inputs and the preview/confirm protocol, so an agent can call it correctly. The only gap is the shape of the eventual success response (e.g. the new ad group's id), which is left unstated.

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 is 3, but the description adds real meaning: it states where pcChannelId/mobileChannelId come from (existing ad group listing, or the admin screen as fallback) and warns that bidAmt/dailyBudget/budget are not accepted even though the schema simply omits them. It also restates the confirmation_token semantics, though that duplicates the schema description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names a specific verb and resource with scope: creating exactly one ad group under a campaign. It then enumerates the fields that identify that group (nccCampaignId, name, adgroupType, pcChannelId, mobileChannelId), so an agent knows precisely what operation and what inputs constitute it.

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 prerequisites (Naver Search Ad account must be linked first) and explicit exclusions (don't pass bidAmt, dailyBudget, budget — such requests are rejected; set those in the admin screen), plus guidance on where to source channel IDs, including the fallback when no ad groups exist. What it omits is routing to siblings for the excluded operations — it never points at adgroups__update for bid/budget changes, which would be the natural alternative.

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?