XBOSS

네이버 검색광고 캠페인 수정

naver_searchad__campaigns__update

Destructive

캠페인 하나를 일시정지하거나 다시 켜거나(userLock), 게재 기간(periodStartDt, periodEndDt, usePeriod)을 바꿉니다. nccCampaignId 는 캠페인 목록 조회에서 얻습니다. 바뀐 결과는 네이버 검색광고의 응답으로 돌려줍니다. 입찰가와 하루 예산은 아직 이 도구로 정하거나 바꿀 수 없습니다. 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": "naver_searchad__campaigns__update"
  }
}

Input Schema

Name	Required	Description
`userLock`	No	true 면 일시정지하고 false 면 다시 켭니다.
`usePeriod`	No	true 면 게재 기간을 적용하고 false 면 없앱니다.
`periodEndDt`	No	게재 종료 일시.
`nccCampaignId`	Yes	캠페인 id(nccCampaignId). 캠페인 목록 조회 결과에서 얻습니다.
`periodStartDt`	No	게재 시작 일시.
`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.4/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing the write-confirmation protocol: the first call only previews and returns WRITE_CONFIRMATION_REQUIRED with a one-time token valid for 10 minutes, and each call consumes one token while creating an XBOSS job. The 'not purely read-only' statement is consistent with readOnlyHint=false and destructiveHint=true. It does not describe failure modes after actual execution or reversibility of a pause, so it falls short of a 5.

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 core action is front-loaded and the confirmation protocol is essential, but the text is long and mixes Korean and English boilerplate. The tail sentences about not being read-only and about XBOSS job creation restate annotation content already supplied, adding bulk without new 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 destructive write tool with no output schema, it covers prerequisites, forbidden parameters, ID sourcing, token lifetime and reuse rules, and notes that the changed result is returned from Naver's response. What remains thin is post-execution behavior, such as what happens to a campaign already paused or how partial updates interact.

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, and the description adds real meaning: it names the exact fields that control pause/resume and period, explains that nccCampaignId comes from the campaign list query, and warns that bidAmt/dailyBudget/budget must never be included. account_link_id is left to the schema, which is acceptable.

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?

States a concrete verb set on a single resource: pause/resume a campaign via userLock, or change the serving period via periodStartDt/periodEndDt/usePeriod. It also carves out what the tool is not for (bid and daily budget), which separates it from generic update siblings such as adgroups__update or ads__update.

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?

Gives explicit routing: bidAmt, dailyBudget and budget requests are rejected, so the user must be directed to the Naver ad management UI. It also states the prerequisite (link a Naver Search Ad account first) and spells out the exact when-to-use sequence for the two-step confirm flow, including the rule that a changed argument invalidates the token and requires a fresh preview.

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?