XBOSS

네이버 검색광고 캠페인 삭제

naver_searchad__campaigns__delete

Destructive

캠페인 하나와 그 아래의 광고그룹, 광고, 키워드를 모두 지웁니다. 되돌릴 수 없으므로 잠시 멈추려면 삭제 대신 일시정지하세요. 지운 뒤 다시 읽어 확인합니다. 먼저 네이버 검색광고 계정을 연동해야 합니다. 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__delete"
  }
}

Input Schema

Name	Required	Description
`nccCampaignId`	Yes	캠페인 id(nccCampaignId). 캠페인 목록 조회 결과에서 얻습니다.
`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?

The description goes well beyond destructiveHint=true: it discloses the cascade of child objects destroyed, states the operation cannot be undone, notes a post-delete re-read for verification, and requires account linking first. It then documents the two-call preview/confirmation protocol, the WRITE_CONFIRMATION_REQUIRED error, and the rule that the token may only be supplied after user agreement. These all match readOnlyHint=false and destructiveHint=true, so there is no annotation contradiction.

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 message is front-loaded, but the text switches between Korean and English mid-paragraph and ends with institutional boilerplate about XBOSS tasks and token consumption that reads as generic and partly garbled. It could be tightened by removing the trailing block and unifying the language.

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 3-parameter destructive tool with no output schema, the definition covers the prerequisites, the destructive scope, the verification behavior, and the full confirmation handshake. An agent has everything it needs to avoid an accidental irreversible deletion.

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 nevertheless adds semantics the schema does not spell out as a flow, namely that changing any argument invalidates the confirmation_token and that a token-free call yields a fresh preview. It adds nothing extra for nccCampaignId or account_link_id, but the token rules are reinforced in context.

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 plus its cascade scope: deleting one campaign along with its adgroups, ads, and keywords. That scope detail lets an agent distinguish it from naver_searchad__adgroups__delete and the other narrow delete siblings without opening a schema.

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 explicitly says the action is irreversible and tells the agent to use pause instead when the intent is only temporary, which is real when-not-to-use guidance. It stops short of naming the pause tool (likely campaigns__update), so the agent must still infer which sibling implements it.

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?