Skip to main content
Glama
Sign In
velog-mcp

velog-mcp

by mrpumpkin98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

벨로그 글 목록

velog_list_posts
Read-only

Retrieve a list of Velog posts from a user, ordered by latest. Optionally filter by tag, limit, cursor, or view only drafts (requires authentication). Uses default username if not specified.

Instructions

벨로그 글 목록을 최신순으로 가져옵니다. username 을 생략하면 VELOG_USERNAME 을 씁니다. drafts_only=True 로 내 임시저장 글만 볼 수 있습니다(인증 필요).

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": "velog_list_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo특정 태그로 필터
limitNo가져올 개수
cursorNo이어서 가져올 기준이 되는 글 UUID
usernameNo벨로그 계정명(@ 제외)
drafts_onlyNo임시저장 글만 조회

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description adds that results are in newest-first order, username defaulting behavior, and authentication requirement for drafts_only. This is valuable behavioral context that the annotations alone do not provide.

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

Conciseness5/5

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

Two sentences with no wasted words. The first sentence states the primary action and ordering; the second adds key usage details. Information is front-loaded and efficient.

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

Completeness5/5

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

For a list tool with 5 parameters, an output schema, and good annotations, the description covers essential points: purpose, ordering, default username, drafts authentication. No critical gaps identified.

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?

The input schema covers all 5 parameters with descriptions (100% coverage). The description adds extra meaning: username default uses an environment variable, and drafts_only requires authentication. These details enhance understanding beyond the schema.

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?

The description clearly states it fetches a list of Velog posts in newest order. It distinguishes itself from sibling tools (e.g., velog_get_post for single post, velog_list_series for series) by focusing on '글 목록' and using the verb '가져옵니다'.

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?

The description provides specific usage context: username defaults to VELOG_USERNAME if omitted, and drafts_only requires authentication. It does not explicitly mention when not to use or compare with alternatives, but the distinct purpose makes it clear when to select this tool.

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

Deploy Server

Other Tools