XBOSS

네이버 검색광고 광고 수정

naver_searchad__ads__update

Destructive

광고 하나를 일시정지하거나 다시 켭니다(userLock). 소재는 바꿀 수 없습니다. nccAdId 는 광고 목록 조회에서 얻습니다. 먼저 네이버 검색광고 계정을 연동해야 합니다. 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": {
      "nccAdId": "<nccAdId>"
    },
    "name": "naver_searchad__ads__update"
  }
}

Input Schema

Name	Required	Description
`nccAdId`	Yes	광고 id(nccAdId). 광고 목록 조회 결과에서 얻습니다.
`userLock`	No	true 면 일시정지하고 false 면 다시 켭니다.
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 서비스에 계정을 여러 개 연동했을 때만 직접 입력해 주세요.
`inspectRequestMsg`	No	심사 요청 메시지(inspectRequestMsg): 반려된 광고의 심사를 다시 요청할 때 적는 글입니다.
`confirmation_token`	No	첫 호출이 돌려준 1회용 확인 토큰입니다(오류 WRITE_CONFIRMATION_REQUIRED). 같은 인자에 이 값을 그대로 넣어 다시 호출하면 실행됩니다. 10분 뒤 만료되고 한 번만 쓸 수 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=true; the description goes well beyond by documenting the preview-first write-confirmation protocol, the WRITE_CONFIRMATION_REQUIRED error, the one-time 10-minute token, token invalidation on argument change, and the rule that the token must never be added without user consent. It also warns that each call consumes a token and creates a XBOSS task, and explicitly says the call is not pure read-only, which is consistent with the annotations.

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 purpose and constraints are front-loaded well, but the description mixes Korean and English, and the closing sentences about token consumption and XBOSS task creation are boilerplate-adjacent and somewhat garbled. Roughly a third of the text does not help an agent decide or invoke correctly.

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 mutating tool with no output schema, the definition covers prerequisites, ID sourcing, side effects, the confirmation flow, and what the first call returns (a preview), which is the essential missing piece. Only the vague XBOSS/account-original sentences leave residual ambiguity about downstream effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter including confirmation_token, account_link_id, and inspectRequestMsg is already documented in the schema. The description restates userLock's pause/resume semantics and the nccAdId provenance, adding little beyond what the schema provides; its added value is mostly procedural rather than per-parameter.

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 statement: pause or resume a single ad via userLock. It also explicitly bounds the scope by stating that creatives cannot be changed, so an agent immediately knows this is a state-toggle, not a general edit, distinguishing it from ads__create/ads__delete.

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 the prerequisite (link the Naver Search Ad account first), the source of the required ID (ad list lookup), and a detailed when/how sequence for the two-step confirmation. It stops short of naming sibling alternatives such as ads__delete or ads__create, but the explicit exclusion of creative changes covers most routing ambiguity.

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?