XBOSS

네이버 검색광고 캠페인 만들기

naver_searchad__campaigns__create

Destructive

연동한 네이버 검색광고 계정에 캠페인 하나를 만듭니다. name 과 campaignTp(WEB_SITE, SHOPPING, POWER_CONTENTS, BRAND_SEARCH, PLACE 중 하나)를 넣습니다. 새 캠페인은 일시정지 상태로 만들어집니다. 광고를 내려면 네이버 검색광고 관리 화면에서 하루 예산을 정한 뒤 켜도록 안내하세요. 결과를 알 수 없을 때 다시 부르지 마세요. 두 번째 호출이 캠페인을 하나 더 만들 수 있습니다. 입찰가와 하루 예산은 아직 이 도구로 정하거나 바꿀 수 없습니다. 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": {
      "campaignTp": "<campaignTp>",
      "name": "<name>"
    },
    "name": "naver_searchad__campaigns__create"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	캠페인 이름.
`campaignTp`	Yes	캠페인 유형.
`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.7/5.0

Behavior5/5

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

Annotations only supply readOnly=false and destructive=true; the description goes far beyond them. It discloses that campaigns are created paused, that enabling requires a console step, that duplicate calls create duplicate campaigns, that a first call returns only a preview plus a one-time token (WRITE_CONFIRMATION_REQUIRED, 10-minute expiry, argument changes invalidate it), and that each call consumes a token and spawns an XBOSS job.

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?

Purpose is front-loaded and the budget restriction is clearly stated, but the confirmation-token flow is explained twice (English block plus Korean preamble) and the trailing boilerplate about XBOSS jobs and institutional writes is generic platform text that does not help an agent call this specific tool. Roughly a third of the text is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating, two-phase-confirmation tool with no output schema, the description covers everything an agent needs: prerequisite account linking, the exact two-call protocol, what the first response contains, token lifetime and invalidation rules, the resulting campaign state, and the non-retryable failure mode.

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 name, campaignTp, account_link_id and confirmation_token are already documented, and the description's restatement of the enum adds little. It does earn extra credit by warning that bidAmt, dailyBudget and budget are rejected outright — a parameter-level trap the schema cannot express, since those fields are absent from it.

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 description opens with a precise verb+resource in a single clause ('연동한 네이버 검색광고 계정에 캠페인 하나를 만듭니다') and immediately names the two required inputs. Sibling tools (campaigns__read/update/delete, adgroups__create) are trivially distinguishable from a single-campaign creation tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit prerequisites are given ('먼저 네이버 검색광고 계정을 연동해야 합니다'), explicit exclusions are given (bidAmt/dailyBudget/budget requests are rejected, go to the Naver console instead), and the retry rule is stated ('결과를 알 수 없을 때 다시 부르지 마세요'). This is the when/when-not/alternative pattern at full strength.

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?