XBOSS

티스토리 글쓰기 임시저장

tistory__retired_openapi__publish

Destructive

Saves the customer's content to the connected Tistory blog as a draft. It does NOT publish: the final publish is always done by the customer in Tistory. Pass document; optionally pass sequence to save into an existing draft, otherwise a new draft is created. The content is the customer's. Connect the Tistory blog first. 호출마다 토큰 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": "tistory__retired_openapi__publish"
  }
}

Input Schema

Name	Required	Description
`document`	Yes	The post content to save as a draft (never published).
`sequence`	No	Existing draft number to save into. Omit to create a new draft.
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 서비스에 계정을 여러 개 연동했을 때만 직접 입력해 주세요.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Beyond the annotations, it discloses that each call consumes a token, creates an XBOSS task, and is not purely read-only, adding useful side-effect and cost context. The appended Korean text about institution data is somewhat confusing, but it still contributes transparency about side effects.

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 English guidance is front-loaded and clear, but the appended Korean sentences about XBOSS task creation and institution data are irrelevant to a Tistory blog draft tool and do not earn their place. This extraneous content reduces overall conciseness and clarity.

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?

For a write operation with three parameters and a nested object, the description covers the prerequisite, content ownership, token cost, and side effects sufficiently for correct invocation. Missing error-handling details are minor given the full schema and annotations.

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 schema already documents all parameters thoroughly. The description reiterates document and sequence semantics but adds no new syntax, constraints, or meaning beyond what the schema provides.

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 clearly states the tool saves content as a draft and explicitly does not publish, distinguishing it from the publish action implied by its name. However, it does not name any sibling tool as an alternative, so it falls short of full sibling differentiation.

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 the prerequisite to connect the Tistory blog first and explains how to use the optional sequence parameter to save into an existing draft versus creating a new one. It does not name alternatives or provide explicit when-not-to-use guidance, but the context is clear.

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?