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

hashnode-mcp-server

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get a single Hashnode post by slug

hashnode_get_post
Read-onlyIdempotent

Fetch full details of a published post by its slug, including content, views, tags, cover image, and author, to retrieve blog post data for display or analysis.

Instructions

Fetch full details of a published post by its slug.

Args:

  • host (string, required): Publication host

  • slug (string, required): Post slug from the URL, e.g. "my-first-post"

  • response_format: 'markdown' or 'json'

Returns: full post data including content brief, views, tags, cover image, author

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": {
      "host": "<host>",
      "slug": "<slug>"
    },
    "name": "hashnode_get_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesPublication host
slugYesPost slug from URL
response_formatNoOutput format: 'markdown' (default) or 'json'markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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
  2. First observedv1.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety needs no restating. The description adds value beyond them by disclosing the returned field set (content brief, views, tags, cover image, author), which matters since there is no output schema, and by implying drafts are out of scope.

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 lead sentence is front-loaded and the whole definition is short. The Args block is mostly redundant with a fully-described schema, with the slug example being the only part that earns its place, so it is not a clean 5.

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 3-parameter read tool with full annotation coverage, the definition covers purpose, inputs, and return shape. Minor gaps remain: behavior for a not-found or unpublished slug, and what 'content brief' means in the response.

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 description adds a concrete slug example ('my-first-post') and clarifies the slug comes from the URL, but restates host and response_format largely as the schema already documents them.

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?

Specific verb+resource: 'Fetch full details of a published post by its slug.' The word 'published' scopes it away from the draft tools and 'single post' distinguishes it from hashnode_list_posts. It does not name a sibling explicitly, so it stops short of a 5.

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?

Usage is implied by 'by its slug' and 'published post', so an agent can infer this is the single-record lookup path. However, there is no explicit guidance such as 'use hashnode_list_posts to discover slugs first' or what happens with a draft slug, leaving the alternative routing to inference.

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