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

hashnode-mcp-server

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List published posts in a Hashnode publication

hashnode_list_posts
Read-onlyIdempotent

Retrieve published Hashnode blog posts ordered newest first, with pagination and Markdown or JSON output for reviewing or managing publication content.

Instructions

List published blog posts in a publication, ordered by publish date (newest first).

Args:

  • host (string, required): Publication host, e.g. "yourblog.hashnode.dev"

  • limit (number): Posts per page (default 20, max 50)

  • after (string): Cursor for pagination

  • response_format: 'markdown' or 'json'

Returns: posts with id, title, slug, url, publishedAt, views, readTime, tags

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>"
    },
    "name": "hashnode_list_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesPublication host, e.g. 'yourblog.hashnode.dev'
afterNoPagination cursor from previous response
limitNoPosts per page
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, so the safety profile is covered. The description adds ordering (newest first), the paging model (limit/after cursor), and the returned fields, which is real context beyond the annotations, though auth requirements and rate limits are unmentioned.

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?

One front-loaded sentence followed by a compact Args/Returns layout; nothing is buried and there is no filler. The Args block is partly redundant with the schema, which keeps it from a 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?

With no output schema, the description does the necessary work by enumerating returned fields (id, title, slug, url, publishedAt, views, readTime, tags) and explaining the pagination cursor. It is missing only caveats about errors or how to obtain the initial cursor.

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%, and the Args block largely restates what the schema already documents (defaults 20/max 50, enum for response_format, cursor semantics). Baseline 3 is appropriate since the description adds no meaning the schema lacks.

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?

States a specific verb and resource ("List published blog posts in a publication") plus an ordering guarantee. The word "published" implicitly differentiates it from the hashnode_list_drafts sibling, but no sibling is named, so an agent still has to infer the boundary against hashnode_get_post.

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 only implied by "published". The description never says when to prefer this over hashnode_get_post (single post) or hashnode_list_drafts, and gives no preconditions such as needing a valid publication host.

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