Skip to main content
Glama
Sign In
MisarBlog MCP Server

MisarBlog MCP Server

by Misar-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create series

create_series

Create a new series to group related articles, with a title and optional description for organizing blog content.

Instructions

Create a new series to group related articles

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>"
    },
    "name": "create_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesSeries title
descriptionNoShort description of the series

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed2 schema fields changedv5.1.3
    • changedInput schema / properties / description / description
      Previous value: -"Short summary shown on the series page. Optional."New value: +"Short description of the series"
    • changedInput schema / properties / title / description
      Previous value: -"Display name of the series. The slug is derived from this."New value: +"Series title"
  3. Changed2 schema fields changedv5.1.0
    • 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."
  4. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the safety basics are covered. The description adds nothing beyond that: it does not mention that non-idempotent calls may create duplicate series with the same title, nor what is returned or whether the series is immediately visible.

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?

A single front-loaded sentence with no filler, so it is efficient and easy to scan. It is arguably too terse for the information an agent needs, but there is no wasted wording.

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

Completeness3/5

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

For a simple two-parameter creation tool with full schema coverage and annotations covering safety, the description is minimally adequate. It omits the return value (e.g. the new series identifier needed for add_to_series), which matters for the surrounding workflow.

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%, with both title and description documented in the schema, so the baseline is 3. The description adds no extra meaning about title uniqueness, length constraints, or whether description is optional.

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 description gives a specific verb and resource ('Create a new series') plus the intent ('group related articles'), so an agent can tell it apart from create_draft or add_to_series by outcome. It stops short of explicitly naming the sibling tools it differs from.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when to create a series versus adding an article to an existing one via add_to_series, and no prerequisites such as authentication. The grouping intent only weakly implies usage.

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