velog-mcp

get_user_posts

Retrieve a list of posts published by a specific Velog user. Supports pagination with cursor and adjustable post limits.

Instructions

Get a list of posts by a Velog user

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": {
      "username": "<username>"
    },
    "name": "get_user_posts"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Number of posts to fetch
`cursor`	No	Cursor for pagination (post ID)
`username`	Yes	Velog username

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 1, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states what is retrieved, but fails to mention pagination behavior (cursor/limit), ordering, or any caveats like whether drafts are included. This lack of behavioral detail is a notable gap for a tool with pagination.

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?

The description is a single, clear sentence with no wasted words. It is front-loaded with the verb and resource.

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?

The tool is relatively simple, but the description omits how pagination works, what the response structure looks like (no output schema), and any error conditions. Given the presence of cursor and limit parameters, the description is somewhat incomplete for an agent to use it fully without further investigation.

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 three parameters. The description adds no parameter-specific meaning beyond the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Get') and resource ('list of posts') with an explicit scope ('by a Velog user'), distinguishing it clearly from siblings like get_trending_posts, search_posts, and read_post.

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

Usage Guidelines3/5

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

The description implies usage: use this to retrieve a specific user's posts. However, it does not explicitly contrast with alternatives such as search_posts or get_trending_posts, nor mention when not to use it.

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

Deploy Server