Skip to main content
Glama

Misar.Blog MCP Server

by io.github.Misar-AI

Create a series

create_series

Create a new, empty series — a named collection that related articles can be added to.

Creating the series does not move any article into it; follow up with add_to_series for each one. Call get_series first to avoid making a second series with the same title, since each call creates a NEW series and nothing deduplicates them.

Requires an API key. The series and its URL become publicly reachable, though it shows nothing until articles are added. Returns the series with the slug that add_to_series needs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesDisplay name of the series. The slug is derived from this.
descriptionNoShort summary shown on the series page. Optional.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"Short description of the series"New value: +"Short summary shown on the series page. Optional."
    • changedInput schema / properties / title / description
      Previous value: -"Series title"New value: +"Display name of the series. The slug is derived from this."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations, the description discloses non-idempotency ('each call creates a NEW series'), public visibility of the series URL, requirement of an API key, and the return value including the slug needed by add_to_series.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each serving a distinct purpose: core function, usage guidance, and behavioral/return details. No redundancy or filler, with the most important information front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description compensates by explaining the return value (slug), side effects (public URL), and the recommended sequence with get_series and add_to_series. This is complete for a simple creation 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?

Schema description coverage is 100%, with both title and description already documented. The description adds little new parameter-level meaning beyond what the schema provides, so baseline 3 is appropriate.

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?

The description clearly states 'Create a new, empty series' with a specific verb and resource, and clarifies that it does not move articles into the series, distinguishing it from the sibling tool add_to_series.

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?

The description explicitly instructs to call get_series first to avoid duplicates and to follow up with add_to_series for each article, providing clear when-to-use and alternative steps.

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

All Misar.Blog MCP Server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Tools have clear, distinct purposes. Even similar tools like generate_title_seo and suggest_titles are clearly separated by input type (topic vs draft). The descriptions are exhaustive, preventing confusion.

Naming Consistency5/5

All tools use lowercase snake_case with verb-first naming. Slight inconsistency: 'upgrade' is a bare verb while others are verb_noun, but overall pattern is consistent.

Tool Count4/5

23 tools is a large but justifiable set for a full-featured blogging platform covering articles, series, reactions, newsletter, analytics, and AI assistance. It borders on the high end but remains scoped.

Completeness2/5

The tool set covers creation, publishing, updating, and listing of articles, but lacks delete operations for articles and series, and offers no comment management beyond reading. This leaves notable lifecycle gaps.

Resources