XBOSS

네이버 검색광고 광고 삭제

naver_searchad__ads__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": {
      "nccAdId": "<nccAdId>"
    },
    "name": "naver_searchad__ads__delete"
  }
}

Input Schema

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

Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds substantial context beyond them: irreversibility, a post-delete re-read verification step, single-use/10-minute token expiry, per-call token consumption, and the creation of an XBOSS task with stored results. The confirmation-token protocol is the kind of behavior an agent could not infer from annotations alone.

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 critical facts (delete, irreversible, confirm-then-execute) are front-loaded, which is good. However, the trailing institutional boilerplate ('호출마다 토큰 1소진 … XBOSS 작업을 생성하고 … 순수 읽기 전용이 아닙니다') is templated, partly repeats the destructive annotation, and mixes languages, diluting an otherwise tight description.

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 destructive, no-output-schema mutation, the definition supplies everything an agent needs: prerequisite account linking, irreversibility, verification-after-delete, and the full preview/confirm token workflow including expiry and reuse rules. Nothing essential to calling it correctly is missing.

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 nccAdId and account_link_id are already documented and the baseline would be 3. The description adds real procedural meaning for confirmation_token (why it is absent on the first call, why changing any argument invalidates it, and how to obtain a fresh preview), which goes beyond the schema's field-level text.

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?

States a specific verb and resource ('광고 하나를 지웁니다' – deletes one ad) and scopes it to a single entity, so it is clearly distinguishable from ads__read/update/create by name. It does not explicitly route the agent to sibling delete tools (adgroups__delete, campaigns__delete), so it stops short of full sibling differentiation.

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?

Gives a hard prerequisite (Naver Search Ad account must be linked first) and a precise two-step usage protocol: call without token to get a preview, then re-call with the same arguments plus the token only after user agreement. It does not cover when-not-to-use (e.g., pausing via ads__update instead of deleting), which keeps it from a 5.

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?