Skip to main content
Glama
Sign In
hashnode-mcp-server

hashnode-mcp-server

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update a published Hashnode post

hashnode_update_post

Update an already-published Hashnode post, modifying only the fields you specify.

Instructions

Update fields of an already-published post. Only provided fields are changed.

Args:

  • post_id (string, required): Post ID (from hashnode_list_posts or hashnode_get_post)

  • title (string, optional): New title

  • content_markdown (string, optional): New content in Markdown

  • subtitle (string, optional): New subtitle

  • tags (array, optional): New tags [{ name, slug }]

  • cover_image_url (string, optional): New cover image URL

  • response_format: 'markdown' or 'json'

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_update_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoNew tags [{ name, slug }]
titleNoNew title
post_idYesPost ID to update
subtitleNoNew subtitle
cover_image_urlNoNew cover image URL
response_formatNoOutput format: 'markdown' (default) or 'json'markdown
content_markdownNoNew content in Markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.3
    • 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
    • removedInput schema / properties / tags / items / additionalProperties
      Removed value: -false
  2. First observedv1.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the safety profile, but the description adds useful behavioral detail: only provided fields are changed, making the partial-update semantics explicit. It still leaves some mutation context unstated, such as whether updates affect live content immediately or what response is returned.

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

Conciseness4/5

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

The key information is front-loaded in the first sentence, and the Args list is easy to scan. The list mostly mirrors the schema, which is mildly redundant, but there is no significant filler.

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?

For a mutation tool with no output schema, the description does not explain what successful updates return or how errors are surfaced, despite exposing response_format. It is still adequate to invoke the tool, but not fully complete for the mutation context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the schema already documents every parameter, so the baseline is 3. The description adds some value by noting that post_id comes from hashnode_list_posts or hashnode_get_post and by summarizing response_format.

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 states a specific verb and resource: updating fields of an already-published post. The phrase 'already-published' meaningfully distinguishes it from the sibling hashnode_update_draft, which handles drafts.

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?

It gives clear context for when to use the tool: when modifying a post that is already published. It does not explicitly name hashnode_update_draft or state exclusions, but the published-only condition is enough to guide selection.

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