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

hashnode-mcp-server

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get current Hashnode user and their publications

hashnode_get_me
Read-onlyIdempotent

Access your Hashnode user profile and list your existing blog publications. Discover your specific publication IDs to manage drafts and posts.

Instructions

Returns the authenticated user's profile and a list of their publications. Use this first to discover your publicationId(s) before creating or listing posts.

Returns:

  • id, name, username, profilePicture

  • publications[]: { id, title, url }

Examples:

  • "What is my publication ID?" → call hashnode_get_me

  • "List my Hashnode blogs" → call hashnode_get_me

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hashnode_get_me"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds the valuable disclosure of exactly what is returned (id, name, username, profilePicture, publications[]). It does not mention auth scope, pagination or limits, but for a no-arg identity read the disclosed payload shape is sufficient context.

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 purpose, then usage rule, then a compact return-field list, then examples — all short and scannable. The two examples largely restate the same intent ('my publication ID' vs 'my blogs'), so one could be dropped without loss.

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 correctly enumerates return fields, and the discovery-first usage rule covers the main coordination need with siblings. Nothing about error cases or empty-publication behavior, but that is minor for a single-optional-param read tool.

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?

Only one optional parameter (response_format) with 100% schema description coverage, so baseline is 3. The description never mentions the output-format option, leaving the schema as the sole source of that information.

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?

States a specific verb+resource (returns the authenticated user's profile and their publications) and distinguishes itself from siblings by framing itself as the publicationId discovery step rather than a post/listing tool. Name, title and description align without redundancy.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this first to discover your publicationId(s) before creating or listing posts,' which gives a clear ordering rule relative to hashnode_create_draft, hashnode_list_posts and the rest. The example phrasings map concrete user intents to this tool.

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