XBOSS

네이버 검색광고 광고그룹 삭제

naver_searchad__adgroups__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": {
      "nccAdgroupId": "<nccAdgroupId>"
    },
    "name": "naver_searchad__adgroups__delete"
  }
}

Input Schema

Name	Required	Description
`nccAdgroupId`	Yes	광고그룹 id(nccAdgroupId). 광고그룹 목록 조회 결과에서 얻습니다.
`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

A3.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the bar is lower, yet the description adds real substance: irreversibility, a post-delete read-back verification, an account-linking prerequisite, and the full two-phase write-confirmation protocol (preview returned first, token required, argument changes invalidate the token). It is diluted by generic boilerplate about XBOSS jobs and "토큰 1소진" that does not describe this tool's concrete behavior, and the trailing note restates non-read-only status already implied by 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 delete-and-irreversible statement is front-loaded and the confirmation procedure is logically ordered, but the body mixes Korean and English boilerplate ("This writes to the institution", XBOSS 작업 생성, 기관 원본 조회) that reads as templated filler rather than tool-specific content. Roughly a third of the text does not earn its place.

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 single-parameter tool with no output schema, the description covers the essentials an agent needs to call it correctly: prerequisite linking, preview-then-confirm sequencing, irreversibility, and verification after deletion. Only the token-burn/audit boilerplate remains unclear and could confuse an agent about side effects.

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 description coverage is 100%, so the baseline is 3, but the description adds flow-level meaning the schema cannot: the first call executes nothing and returns a preview, the same arguments plus the token execute it, and changing any argument forces a fresh preview. This explains how confirmation_token interacts with the other parameters rather than merely restating field docs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"광고그룹 하나를 지웁니다" names a specific verb (delete) and resource (one adgroup), and the immediately following "되돌릴 수 없습니다" frames the operation's nature. It is clearly distinct from adgroup create/read/update and from ads/keywords/campaigns deletes, though it never explicitly contrasts itself with those siblings.

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

Usage Guidelines3/5

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

The description states a prerequisite ("먼저 네이버 검색광고 계정을 연동해야 합니다") and a detailed call procedure for the confirmation handshake, which is useful usage context. However, it gives no guidance on when to delete an adgroup versus pausing/updating it, and no explicit when-not conditions or named alternatives.

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?