hashnode-mcp-server

List Hashnode drafts

hashnode_list_drafts

Read-onlyIdempotent

Retrieve and review drafts in a Hashnode publication with pagination, returning IDs, titles, subtitles, tags, and update dates for content planning and editing.

Instructions

List drafts in a Hashnode publication.

Args:

publication_id (string): The publication ID (from hashnode_get_me)
limit (number): Number of drafts to return (default 20, max 50)
after (string): Pagination cursor from a previous call
response_format: 'markdown' or 'json'

Returns: list of drafts with id, title, subtitle, tags, updated date

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": {
      "publication_id": "<publication_id>"
    },
    "name": "hashnode_list_drafts"
  }
}

Input Schema

Name	Required	Description	Default
`after`	No	Pagination cursor from previous response
`limit`	No	Number of drafts to return
`publication_id`	Yes	Publication ID (from hashnode_get_me)
`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

A3.7/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real context on top: default and maximum page size, the meaning of the pagination cursor, and the fields returned for each draft.

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?

Front-loaded with the purpose, then a compact args block and a one-line returns summary. The args block partly duplicates the schema, which costs a little, but nothing is padded or vague.

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 returns line usefully names the draft fields an agent will receive. Pagination and page-size behavior are covered, leaving only minor gaps such as whether drafts are ordered or what happens when the cursor is exhausted.

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 all four parameters are already documented in structured form, setting the baseline at 3. The description adds only the provenance hint 'from hashnode_get_me' and otherwise restates the schema's defaults and enum values.

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 ('List') and resource ('drafts') scoped to a publication, which is unambiguous. It does not explicitly differentiate itself from the sibling hashnode_list_posts, though the draft-vs-post noun distinction is largely self-evident.

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?

The parameter docs imply a prerequisite chain by stating publication_id comes from hashnode_get_me, which is genuinely useful routing information. However, there is no explicit statement of when to use this versus hashnode_list_posts or when pagination requires another call.

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

Deploy Server