Skip to main content
Glama

네이버 블로그 글쓰기 임시저장

naver__blog__post_via_retired_api__publish
Destructive

연결한 내 네이버 블로그에 고객의 글을 임시저장합니다. document 에 글을 넣으세요. log_no 에 기존 초안 번호를 주면 그 초안에 이어서 저장해 같은 번호를 돌려주고, 주지 않으면 새 초안을 만듭니다. 임시저장 목록에 없는 번호면 저장하지 않고 초안을 찾지 못했다는 오류가 납니다. 발행은 하지 않습니다. 최종 발행은 고객이 네이버 블로그에서 직접 하고, 글의 내용은 고객의 것입니다. 네이버 계정을 먼저 연결해야 합니다. 호출마다 토큰 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": {
      "document": "<document>"
    },
    "name": "naver__blog__post_via_retired_api__publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
log_noNo이어서 저장할 기존 임시저장 글 번호(logNo). 입력하지 않으면 새로 임시저장합니다.
documentYes임시저장할 글 내용. 발행하지 않습니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 서비스에 계정을 여러 개 연동했을 때만 직접 입력해 주세요.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / document / description
      Previous value: -"The post content to save as a draft (never published)."New value: +"임시저장할 글 내용. 발행하지 않습니다."
    • changedInput schema / properties / document / properties / categoryId / description
      Previous value: -"Naver blog category id. Optional."New value: +"선택 입력. 네이버 블로그 카테고리 번호."
    • changedInput schema / properties / document / properties / rights_declared / description
      Previous value: -"Must be true - the customer declares they hold the rights to publish this content."New value: +"true 여야 합니다. 이 글을 게시할 권리가 고객에게 있다고 밝히는 값입니다."
    • changedInput schema / properties / document / properties / tags / description
      Previous value: -"Comma-separated tags. Optional."New value: +"선택 입력. 쉼표로 구분한 태그."
    • changedInput schema / properties / document / properties / title / description
      Previous value: -"The post title."New value: +"글 제목."
    • changedInput schema / properties / log_no / description
      Previous value: -"Existing draft number (logNo) to save into. Omit to create a new draft."New value: +"이어서 저장할 기존 임시저장 글 번호(logNo). 입력하지 않으면 새로 임시저장합니다."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true. The description adds real behavior beyond them: 1 token per call, an XBOSS job created per call, a prerequisite Naver account link, the not-found error path, and the fact that no publication occurs. The main gap is that it never explains what happens to the existing draft's content when log_no is supplied, which matters given destructiveHint=true.

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 core drafting and log_no behavior is front-loaded and useful. The trailing sentences about another institution's data, XBOSS job creation and permission boilerplate are templated and dilute the focus, while the token cost detail is relevant but buried.

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?

No output schema exists, so the description carries return information, and it explains that passing log_no returns the same draft number, though it never states what a newly created draft returns. Prerequisites, error paths and the no-publish guarantee are covered, which is adequate for a 3-parameter nested mutation tool.

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?

With 100% schema description coverage, the baseline is 3, but the description adds meaning beyond the schema by explaining that log_no continues an existing draft and returns the same number, and that new drafts are created when it is absent. It also frames document as the post content, though it adds nothing for account_link_id beyond what the schema states.

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 verb and resource: saving a customer's post as a draft (임시저장) on the connected Naver blog, and explicitly contrasts this with publishing ("발행은 하지 않습니다"). The intended operation is clear despite the tool name containing 'publish', which conflicts with the actual drafting behavior. It does not name a sibling tool, so it falls short of 5.

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 conditions: put the post in document; pass log_no to continue an existing draft, omit it to create a new one; a log_no not in the draft list yields a 'draft not found' error; a Naver account must be connected first. It does not compare against a sibling tool that might handle publishing or creating.

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