Skip to main content
Glama

네이버 검색광고 비즈머니 잔액 조회

naver_searchad__bizmoney__read

조회만 합니다. 연동한 네이버 검색광고 계정의 비즈머니(bizmoney) 잔액과 그 계정의 budgetLock, refundLock 값을 돌려줍니다. 먼저 네이버 검색광고 계정을 연동해야 합니다. 로그인한 호출이면 첫 요청 전에 request_idempotency_key 값을 만들어 저장하세요. 응답을 받지 못한 그 요청을 되찾을 때만 같은 인자와 함께 그 값을 다시 보내고, 새로 실행할 때는 새 값을 쓰세요. 이 값 없이 다시 부르면 새 요청이 됩니다. 계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다. 기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "naver_searchad__bizmoney__read"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 서비스에 계정을 여러 개 연동했을 때만 직접 입력해 주세요.
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / request_idempotency_key / description
      Previous value: -"Optional same-request recovery key for authenticated calls; see the tool description."New value: +"로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false) by disclosing that each call consumes one token, creates an XBOSS task, and stores the processing result, and explicitly warns that the call is not purely read-only despite being a balance inquiry. It also spells out the resend-vs-new-request semantics of the idempotency key.

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 operational facts are useful but the text is padded with administrative boilerplate ('기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요') and opens with '조회만 합니다' (only reads) before later saying the call is not purely read-only, which muddles the front-loaded message.

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?

With no output schema, the description carries the return-value burden and does so partially, naming balance, budgetLock, and refundLock. It also covers the account-linking prerequisite and token cost; currency/format and error behavior remain unspecified, so it is not fully complete.

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 documents both optional fields (baseline 3), but the description adds real usage semantics for request_idempotency_key — the store-before-first-call and resend-only-to-recover rules — and notes that the optional field cannot be used when calling without an account. The meaning of '이 선택 칸' is ambiguous about which parameter it refers to.

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?

States a specific verb+resource: it returns the bizmoney balance plus budgetLock and refundLock for the linked Naver Search Ad account. That is clearly distinct from the read-only siblings (adgroups, ads, campaigns, keywords), so an agent can tell what this tool is for without opening the 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?

Gives a concrete precondition ('먼저 네이버 검색광고 계정을 연동해야 합니다') and explains the idempotency-key workflow: create and store a key before the first request, resend the same key only to recover an unanswered request, use a fresh key for a new execution. It does not name a sibling alternative or state when-not to call it, which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources