XBOSS

네이버 검색광고 키워드 수정

naver_searchad__keywords__update

Destructive

키워드 하나를 일시정지하거나 다시 켭니다(userLock). nccKeywordId 는 키워드 목록 조회에서 얻습니다. 입찰가와 하루 예산은 아직 이 도구로 정하거나 바꿀 수 없습니다. 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": {
      "nccKeywordId": "<nccKeywordId>",
      "userLock": "<userLock>"
    },
    "name": "naver_searchad__keywords__update"
  }
}

Input Schema

Name	Required	Description
`userLock`	Yes	true 면 일시정지하고 false 면 다시 켭니다.
`nccKeywordId`	Yes	키워드 id(nccKeywordId). 키워드 목록 조회 결과에서 얻습니다.
`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.5/5.0

Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=true; the description goes much further. It explains the two-call write-confirmation protocol: the first call returns a preview plus a one-time confirmation_token (WRITE_CONFIRMATION_REQUIRED), the token must not be added without user agreement, changing any argument invalidates it, and each call consumes one token. It also discloses that the call creates an XBOSS job and is not a pure read — well beyond the annotation layer.

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 its constraint are front-loaded in the first two sentences, which is good. However, the confirmation-token procedure is spelled out at length and then largely repeated in the confirmation_token schema description, and the trailing institutional boilerplate about XBOSS jobs and per-tool confirmation procedures is generic filler that does not help an agent call this tool.

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, confirmation-gated tool with no output schema, the description covers everything needed: the id source, account-link precondition, rejected fields, the exact two-step invocation sequence, and token expiry. An agent could invoke this correctly on the first attempt without consulting anything else.

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. The description earns above baseline by documenting behavior for parameters the schema does not contain at all — bidAmt, dailyBudget and budget are rejected outright — which prevents an agent from attempting a bid change through this tool. The token lifecycle is restated in the description but also present in the schema, so it adds less.

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?

"키워드 하나를 일시정지하거나 다시 켭니다(userLock)" states a specific verb (pause/resume), a specific resource (one keyword), and the exact field that carries it. It also scopes out what the tool does not do (bid and daily budget), which separates it cleanly from keywords__create, keywords__delete and keywords__read.

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 concrete preconditions: obtain nccKeywordId from the keyword list, and link the Naver Search Ad account first. It also states an explicit exclusion — requests carrying bidAmt, dailyBudget or budget are rejected and the user should be directed to the Naver ad management UI. It stops short of naming a sibling tool for bid changes, so it is clear but not fully routing.

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?