Skip to main content
Glama
Sign In
velog-mcp

velog-mcp

by mrpumpkin98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

벨로그 글 삭제

velog_delete_post
Destructive

Delete a Velog post permanently by providing its UUID and setting confirm=true to prevent accidental removal.

Instructions

글을 삭제합니다. 복구할 수 없으므로 confirm=True 를 명시해야 실행됩니다.

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": {
      "post_id": "<post_id>"
    },
    "name": "velog_delete_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo삭제를 확인. True 여야 실행된다
post_idYes삭제할 글 UUID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds valuable context that the action is irreversible and requires explicit confirmation, which goes beyond what annotations 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?

The description is extremely concise: one sentence for the action and one for the warning. No redundant words, every sentence adds value.

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 simple destructive tool with output schema present, the description covers the core action, irreversibility, and required confirmation. It lacks mention of error cases or side effects, but these are minor gaps.

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 coverage is 100%, so the schema already documents both parameters. The description adds emphasis on the confirm=True requirement, but does not provide new semantics beyond what the schema offers.

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 explicitly states '글을 삭제합니다' (deletes a post), clearly identifying the verb and resource. Among sibling tools which include create, update, list, get, etc., this uniquely identifies the delete action.

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 clearly states when to use (to delete) and a critical prerequisite ('confirm=True') due to irreversibility. It does not explicitly list when not to use or alternatives, but the context is clear enough for most agents.

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