Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

네이버 검색광고 키워드 목록 조회

naver_searchad__keywords__read

조회만 합니다. 광고그룹 하나에 등록된 키워드 목록을 돌려줍니다. nccAdgroupId 를 넣습니다. nccAdgroupId 는 광고그룹 목록 조회에서 얻습니다. 먼저 네이버 검색광고 계정을 연동해야 합니다. Files: a document generated from this result, as Excel (xlsx) only when requested in output_formats, listed in artifacts[] of the result with a download_url that works for 15 minutes; each file is kept for 7 days. If a link has expired, call xdata__job__result with the job_id from the result for fresh links. For an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane. For an authenticated call, generate and save request_idempotency_key before the first request. Reuse it with the same arguments only to recover that request after a lost response; use a new key for a new execution. Without it, calling again remains a new request. This optional key is not available to anonymous taste calls. Keep any provider-specific idempotency_key unchanged; it is a different field. 호출마다 토큰 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__keywords__read"
  }
}

Input Schema

NameRequiredDescriptionDefault
nccAdgroupIdYesAd group id (nccAdgroupId) from the ad group list.
output_formatsNo선택 입력입니다. 결과를 엑셀(xlsx) 파일로도 받으려면 입력해 주세요. 파일은 결과의 artifacts[] 에 실립니다. 비워 두면 데이터만 받습니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 서비스에 계정을 여러 개 연동했을 때만 직접 입력해 주세요.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

The annotations declare readOnlyHint=false and destructiveHint=false, and the description does add genuinely useful behavior beyond them: one token is consumed per call, an XBOSS job is created and the result is stored. However the opening sentence '조회만 합니다' claims read-only behavior, directly conflicting with readOnlyHint=false and with the later sentence stating the call is not purely read-only. An agent cannot form a coherent picture of side effects from this text.

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 actual tool purpose sits in two short sentences at the top, but they are followed by a long block of copy-pasted artifact, recovery_receipt and idempotency boilerplate that appears unrelated to a keyword listing. The Korean behavioral note is appended at the very end, after the reader has already been buried in irrelevant material. Structure is poor and much text does not earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-style listing with one required parameter and no output schema, the description should clarify what the returned keyword records contain and confirm the read-only nature. Instead it leaves the read/write question self-contradictory and spends most of its length on file retention and receipt rules that do not apply to this lookup. The prerequisites are the only genuinely complete part.

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 the baseline is 3. The description restates that nccAdgroupId is obtained from the ad group list, which the schema already says, and mentions output_formats, request_idempotency_key and account_link_id only through generic boilerplate rather than tool-specific meaning. It adds little semantics 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 second sentence states a specific verb and resource: it returns the list of keywords registered in one ad group. That is concrete enough to distinguish it from naver_searchad__adgroups__read and naver_searchad__ads__read, although the description never explicitly contrasts them. The surrounding text is about files, receipts and idempotency rather than purpose, which dilutes the signal.

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?

It gives real prerequisites: nccAdgroupId must come from the ad group list lookup, and the Naver search ad account must be linked first. It also points to xdata__job__result for expired file links. It offers no when-not guidance and no comparison with sibling read tools, leaving the agent to infer that this is the keyword-level listing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All XBOSS toolsInspect
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