Skip to main content
Glama
Sign In
hatena-blog-mcp

hatena-blog-mcp

by sumiVer2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

固定ページ作成

create_page

Creates a new static page on Hatena Blog as a draft by default; set draft to false to publish or use a future date with scheduled to queue it.

Instructions

固定ページを新規作成する。既定では下書きとして作成されるので、公開する場合は draft を false にする。予約投稿する場合は draft=true・scheduled=true と、未来日時の updated を指定する。 固定ページははてなブログの有料プランでのみ利用できる。無料プランでは 404 が返る。

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": {
      "title": "<title>",
      "content": "<content>"
    },
    "name": "create_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftNo下書きとして保存するか（既定: true）
titleYesタイトル
contentYes本文。ブログの編集モードに合わせた記法で書く
updatedNo投稿日時（ISO 8601、例: 2026-08-26T15:30:00+09:00）。省略時は現在時刻
scheduledNo予約投稿にするか。draft=true かつ updated が未来日時のときに有効
custom_urlNoカスタム URL（記事 URL のスラッグ部分）
content_typeNo本文の記法。実際の解釈はブログの編集モード設定に従うため、ブログ側の設定と揃えること（既定: text/x-markdown）
preview_sharedNo下書きのプレビュー共有 URL を発行するか

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the default draft state, the plan gating, and the concrete failure mode ('無料プランでは404が返る'). It does not say what a successful call returns (page ID/URL) or whether creation is idempotent, which matters for a mutating tool.

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?

Four short sentences, front-loaded with the action and then the draft/publish/schedule decision tree. It slightly restates the schema default (draft=true) rather than only adding new information, but nothing is padded.

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?

Covers the high-risk aspects an agent needs before a write – plan requirement, draft-vs-publish behavior, scheduling. Gaps remain for an 8-parameter mutating tool with no output schema: no indication of the return value (page ID or URL for follow-up update_page/get_page) and no note on how custom_url conflicts are handled.

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?

Schema coverage is 100%, so the baseline would be 3; the description earns a 4 by adding a cross-parameter constraint the schema cannot express – that 'scheduled' is only effective when draft=true and 'updated' is a future timestamp. It adds little about custom_url, preview_shared, or content_type beyond what the schema already documents.

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?

The opening states a specific verb + resource ('固定ページを新規作成する'), which is precise and clearly distinct from the entry-oriented siblings. However, it never explicitly contrasts itself with create_entry, so the agent must infer the page-vs-entry split from the terminology alone.

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 concrete mode-selection rules: created as a draft by default, set draft=false to publish, and draft=true + scheduled=true + a future 'updated' to schedule. It also states the paid-plan precondition, which prevents a wasted call. It stops short of naming alternatives (e.g. use create_entry for posts) or exclusions.

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