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

hatena-blog-mcp

by sumiVer2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

固定ページ検索

search_pages
Read-only

Searches fixed pages by title, body, or category using case-insensitive partial matches, paging through results to find older content; increase max_pages when needed.

Instructions

固定ページをページを辿りながら検索する。タイトル・本文・カテゴリを対象に部分一致（大文字小文字は無視）。はてなブログの API は一覧の 1 ページあたり件数が少ないため、まとめて探すときはこのツールを使う。古い固定ページまで届かない場合は max_pages を増やす。 固定ページははてなブログの有料プランでのみ利用できる。無料プランでは 404 が返る。

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": "search_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo返す最大件数
queryNoタイトル・本文・カテゴリに対する検索語
statusNo公開状態での絞り込みall
max_pagesNo走査する最大ページ数。多いほど古い記事まで届くが時間がかかる
include_contentNo結果に本文を含めるか

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

readOnlyHint=true is consistent with the description, and the text adds real context beyond it: the tool walks result pages internally, raising max_pages costs time, and the call returns 404 on free plans. Return shape and ordering are not described, but the safety and cost profile is well covered.

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-loads purpose, then usage, then the plan prerequisite, with no filler. Minor deduction for the garbled opening ('固定ページをページを辿りながら') and for the max_pages advice that partially duplicates the schema text.

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 read-only, five-parameter search with full schema coverage and no output schema, the description supplies the operational context an agent needs: traversal behavior, cost of raising max_pages, and the plan restriction. Only the result format/ordering is absent, which is minor here.

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%, so all five parameters are already documented, including max_pages' trade-off and include_content. The description only restates the search targets covered by the query parameter, adding essentially no syntax or format detail beyond the schema — baseline 3 applies.

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 (固定ページを…検索する) and enumerates the search targets (タイトル・本文・カテゴリ) along with the matching mode (部分一致、大文字小文字無視). It implies a contrast with a plain listing tool but never names a sibling such as list_pages or search_entries, so differentiation is left to inference.

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?

Gives a clear trigger for choosing this tool ('まとめて探すときはこのツールを使う') and a tuning rule ('古い固定ページまで届かない場合は max_pages を増やす'), plus the paid-plan prerequisite and the 404 on free plans. It stops short of explicitly naming the alternative tools it is meant to replace.

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