XBOSS

네이버 검색광고 키워드 만들기

naver_searchad__keywords__create

Destructive

광고그룹 하나에 키워드를 한 번에 더합니다. nccAdgroupId 와 keywords(keyword 를 담은 객체 목록)를 넣습니다. 키워드 객체에 bidAmt 와 useGroupBidAmt 를 넣지 마세요. 키워드는 광고그룹의 기본 입찰가를 따르고, 새로 만든 광고그룹이면 네이버 최소 입찰가 70원입니다. 입찰가는 네이버 검색광고 관리 화면에서 바꾸도록 안내하세요. 새 키워드는 네이버 심사를 거친 뒤 노출됩니다. 일부만 거절되면 결과에 그 키워드와 사유가 나옵니다. 입찰가와 하루 예산은 아직 이 도구로 정하거나 바꿀 수 없습니다. 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": {
      "nccAdgroupId": "<nccAdgroupId>",
      "keywords": "<keywords>"
    },
    "name": "naver_searchad__keywords__create"
  }
}

Input Schema

Name	Required	Description
`keywords`	Yes	더할 키워드 목록.
`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

A4.2/5.0

Behavior5/5

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

Annotations already declare this is a write (readOnlyHint=false) and destructiveHint=true, and the description adds substantial context beyond that: the two-step preview/confirmation-token flow, token invalidation when arguments change, the account-link prerequisite, Naver review before exposure, partial rejection reporting, and XBOSS task creation. This is exactly the kind of behavior the annotations do not provide.

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 is front-loaded and the confirmation workflow is clearly explained, but bid/budget guidance is repeated in two places and the description mixes Korean with a long English confirmation paragraph. Much of the detail is warranted for a write tool, yet the duplication and language switching keep it from being tight.

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 write tool with no output schema, the description covers prerequisites, side effects, confirmation behavior, review timing, partial failure reporting, and result storage. Almost nothing an agent needs in order to call 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 the schema already defines nccAdgroupId, keywords, account_link_id, and confirmation_token. The description adds useful construction rules beyond the schema, such as not including bidAmt/useGroupBidAmt in keyword objects, rejecting requests with bidAmt/dailyBudget/budget, and reusing the confirmation token with the same arguments. It says little about account_link_id, but overall it adds meaning beyond the schema.

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?

The description states a specific action and scope: it adds keywords to one ad group at a time and identifies the required nccAdgroupId and keywords inputs. It does not explicitly name or differentiate itself from the sibling keyword update/delete tools, so it stops short of the top score.

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 clear preconditions and exclusions: link the Naver Search Ad account first, do not include bid fields in keyword objects, and use the Naver management UI for bids and daily budgets. It does not explicitly compare against sibling keyword tools, but the context is clear enough to guide use.

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?