Skip to main content
Glama

네이버 블로그 글쓰기 필요입력 안내

naver__blog__post_via_retired_api__requirements

자격증명이나 로그인 없이 바로 호출할 수 있습니다. 읽기 전용입니다. 네이버 블로그에 임시저장하려면 넣어야 할 것을 알려 줍니다. 콘텐츠 산출물 참조, 글 제목, 선택인 태그와 카테고리, 꼭 필요한 권리 선언입니다. 이것을 읽는 데는 네이버 연결이 필요 없습니다. 로그인한 호출이면 첫 요청 전에 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__blog__post_via_retired_api__requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

C2.7/5.0
Behavior1/5

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

The description opens with "읽기 전용입니다" (it is read-only), which directly conflicts with the annotations' readOnlyHint=false, and then later reverses itself with "이 호출은 순수 읽기 전용이 아닙니다." Useful side facts are offered (token cost of 1 per call, XBOSS job creation and result storage), but the agent is given contradictory safety signals on the single most important behavioral property.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and the field list are front-loaded and short, but they are followed by unrelated boilerplate about "기관 업무," "기관 원본," and XBOSS that does not belong to a Naver Blog tool, plus a self-contradicting pair of sentences about read-only behavior. Bulk is high while signal is diluted.

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

Completeness3/5

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

For a one-optional-parameter requirements tool with no output schema, the definition does cover the important ground: it lists the inputs the caller will need and explains the idempotency field fully. It is undermined by the read-only contradiction and off-domain institutional text, which leave an agent unsure whether invoking it has side effects such as job creation and token consumption.

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 baseline is 3, and the description genuinely adds semantics beyond the schema: create and store the value before the first logged-in request, reuse the same value only to recover a lost-response request, use a fresh value for a new execution, and note that the anonymous path cannot use this optional field and that the institutional idempotency_key is a different field. That is substantive meaning an agent could not infer from the pattern/length constraints.

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 sentence "네이버 블로그에 임시저장하려면 넣어야 할 것을 알려 줍니다" gives a concrete purpose: a requirements lookup for draft-saving on Naver Blog, and it enumerates the fields it will report (content artifact reference, title, optional tags/category, required rights declaration). It does not name or contrast itself with the sibling write tools (naver__blog__post_via_retired_api__create / publish), so it stops short of a 5.

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

Usage Guidelines2/5

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

It states a qualifying fact (callable without credentials, no Naver connection needed) but never says when to call this versus the create/publish siblings, nor that it should precede a draft write. The only conditional guidance present is about reusing the idempotency key on retries, not about tool selection.

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