Skip to main content
Glama

everyone-builder

draft_post

에브리원 빌더 광장에 올릴 글의 초안을 만듭니다. 이 도구만으로는 공개되지 않습니다 — 돌려받은 주소를 사용자가 브라우저에서 열어 내용을 확인하고 직접 [게시] 를 눌러야 합니다. 반드시 사용자에게 그 주소를 그대로 보여 주고, 열어서 확인해 달라고 전해 주세요. 사용자가 쓰려는 내용을 대신 정리하는 용도이며, 사용자 동의 없이 호출하지 마세요.

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": {
      "category": "<category>",
      "title": "<title>",
      "body": "<body>",
      "authorName": "<authorName>",
      "email": "<email>"
    },
    "name": "draft_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes본문. 사용자가 하려는 말을 그대로 담으세요
tagsNo태그 최대 5개
emailYes작성자 통보용. 공개되지 않습니다
titleYes제목
linkUrlNo소개할 제품·행사 주소
categoryYesshow=만든 것 자랑 · team=팀원 구하기 · event=행사 알림 · hiring=채용 · talk=질문·토론
authorUrlNo기관 홈페이지 (org 일 때 필수)
authorNameYes화면에 보일 이름(닉네임 또는 기관명)
authorTypeNo기관이면 org (홈페이지 주소 필수, 광고로 표시됨)
contactUrlNo오픈채팅·신청폼 등 연락 주소

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses that the write is non-public, that publication requires a separate user action in a browser, and that the tool returns an address the user must be shown. It does not cover failure modes, whether drafts expire, or what the returned payload looks like beyond the address itself.

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

Conciseness4/5

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

Three sentences, front-loaded with what is created and followed immediately by the non-publication caveat and the user-facing obligation. The emphasis markers and the dual instruction to show the URL and ask the user to open it are slightly repetitive but intentionally so for a safety-critical step.

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 10-parameter mutation tool with no annotations and no output schema, the description covers the essential workflow gap: the two-step draft-then-user-publishes model and the returned address. It leaves the exact return shape and error behavior implicit, which is a minor omission given how much it clarifies about the side effects.

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%, including enum explanations for category and authorType, so the schema already does the parameter work. The description only adds framing that the body should capture the user's own intent, which is a mild supplement rather than new semantic detail. Baseline 3 applies.

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 and resource (drafting a post for the Everyone Builder Plaza) and immediately bounds the scope by saying the tool alone does not publish anything. The draft-versus-publish distinction is made explicit, so an agent can tell exactly what this call does and does not accomplish.

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 hard precondition ('사용자 동의 없이 호출하지 마세요') and a required post-call ritual (show the returned address and ask the user to open and confirm it), which is exactly the guidance an agent needs. It stops short of naming an alternative tool or a when-not-to-use scenario beyond the consent rule.

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