Skip to main content
Glama
Sign In
velog-mcp

velog-mcp

by hyungseokyoon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

read_post

Fetch a specific Velog post by username and slug, returning its full content, comments, and metadata.

Instructions

Read a specific Velog post with full content, comments, and metadata

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>",
      "url_slug": "<url_slug>"
    },
    "name": "read_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
url_slugYesPost URL slug
usernameYesVelog username

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.2/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 burden. It discloses that the operation is a read and describes the output content (full content, comments, metadata). It does not mention potential errors, auth requirements, or non-mutation explicitly, but the verb 'Read' implies safety and the output details are valuable.

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?

A single sentence that front-loads the action ('Read a specific Velog post') and then lists the returned data. No wasted words or redundant information.

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?

The description is sufficient for a simple read tool with a clear schema and no output schema. It tells the user what they will get (full content, comments, metadata). It could mention edge cases like nonexistent posts, but for the given complexity, this is complete enough.

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?

The input schema already describes both parameters (username, url_slug) with 100% coverage. The description adds no extra parameter semantics beyond what the schema provides, meeting the baseline.

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 the tool reads a specific Velog post, specifying that it returns full content, comments, and metadata. This distinguishes it from sibling tools like get_user_posts or search_posts, which focus on listing or searching rather than retrieving a single post.

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 implies the intended use case: when you need the complete details of one specific post (using username and url_slug). It clearly differentiates from listing/searching tools but does not explicitly mention alternatives or exclusions, so it stops short of a 5.

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