hashnode-mcp-server

Delete a published Hashnode post

hashnode_delete_post

Destructive

Permanently delete a published post by ID. This action cannot be undone, so use it only when you need to remove the post.

Instructions

Permanently delete a published post. This action cannot be undone.

Args:

post_id (string, required): Post ID to delete
response_format: 'markdown' or 'json'

⚠️ WARNING: This permanently deletes the post.

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

Input Schema

Name	Required	Description	Default
`post_id`	Yes	Post ID to permanently delete
`response_format`	No	Output format: 'markdown' (default) or 'json'	markdown

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.1.3Oct 27, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

First observedv1.1.1Aug 6, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is fully covered. The description's only addition is the word "permanently"/irreversibility, which largely restates the destructive hint; it says nothing about auth requirements, error behavior for a non-existent or draft post, or rate limits.

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

Conciseness3/5

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

Front-loaded and short overall, but the core fact is stated three times: "Permanently delete," "cannot be undone," and "⚠️ WARNING: This permanently deletes the post." The duplicated Args block also repeats the schema verbatim, so several lines do not earn their place.

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 destructive two-parameter tool with full schema coverage and annotations carrying the safety flags, the description plus structured data is nearly sufficient to call it correctly. Minor gaps remain around ownership/auth requirements and what response_format actually changes in the output.

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 baseline is 3. The Args block simply re-lists post_id and response_format with the same wording as the schema, adding no format examples, ID-source hints, or meaning beyond structured data.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

First sentence states a specific verb and resource ("Permanently delete a published post") and the qualifier "published" implicitly scopes it away from drafts. It is clear, but it never names or contrasts any sibling (e.g., hashnode_update_post, hashnode_list_posts) to reinforce the routing decision.

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?

"This action cannot be undone" is a useful guardrail that implies when to be careful, but there is no explicit when-to-use guidance, no alternative (nothing like "to remove a draft use X"), and no stated preconditions such as ownership of the post.

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

Deploy Server