velog-mcp

search_posts

Search Velog posts by keyword. Optionally filter by username and paginate with limit and offset.

Instructions

Search for posts on Velog by keyword

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": {
      "keyword": "<keyword>"
    },
    "name": "search_posts"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Number of results
`offset`	No	Offset for pagination
`keyword`	Yes	Search keyword
`username`	No	Filter by username

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Aug 7, 2026

TDQS

A3.7/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 of behavioral disclosure. It only states the basic action without mentioning pagination behavior, return format, authentication requirements, or any constraints beyond the schema fields. This is a minimal description that leaves key behavioral aspects unexplored.

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, front-loaded sentence with no redundant words. It efficiently communicates the tool's core function.

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, and the schema provides all parameter details. However, with no annotations and no output schema, the description leaves uncertainty about return values and usage nuances in relation to sibling tools. It is adequate but not complete.

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 baseline is 3. The description mentions 'by keyword', which reinforces the keyword parameter but adds no new meaning beyond the schema's own descriptions for limit, offset, and username.

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 a specific verb ('Search'), a resource ('posts'), and a platform ('Velog') with the search scope ('by keyword'). It distinguishes itself from sibling tools like get_user_posts and read_post, which have different purposes.

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 clear context for when to use the tool: when searching for posts by keyword. It does not explicitly mention alternatives or exclusions, but the context is clear enough for the agent to infer its primary use case.

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

Deploy Server