MisarBlog MCP Server

Add to series

add_to_series

Idempotent

Add an existing article to a chosen series, optionally set its position, or append it when no position is provided.

Instructions

Add an existing article to a series

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": {
      "series_slug": "<series_slug>",
      "article_slug": "<article_slug>"
    },
    "name": "add_to_series"
  }
}

Input Schema

Name	Required	Description
`position`	No	Position in the series (optional, appends if omitted)
`series_slug`	Yes	The series slug
`article_slug`	Yes	The article slug to add

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv5.2.0Nov 7, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / position / maximum
```
Added value: +9007199254740991
```

Changed3 schema fields changedv5.1.3Oct 14, 2026

changedInput schema / properties / article_slug / description

Previous value: -"Slug of the article to add, from list_my_articles. Not its title or id."New value: +"The article slug to add"

changedInput schema / properties / position / description

Previous value: -"1-based position within the series. Omit to append at the end. Inserting shifts later articles down."New value: +"Position in the series (optional, appends if omitted)"

changedInput schema / properties / series_slug / description

Previous value: -"Slug of the target series, from get_series. Not its title or id."New value: +"The series slug"

Changed3 schema fields changedv5.1.0Aug 19, 2026

changedInput schema / properties / article_slug / description

Previous value: -"The article slug to add"New value: +"Slug of the article to add, from list_my_articles. Not its title or id."

changedInput schema / properties / position / description

Previous value: -"Position in the series (optional, appends if omitted)"New value: +"1-based position within the series. Omit to append at the end. Inserting shifts later articles down."

changedInput schema / properties / series_slug / description

Previous value: -"The series slug"New value: +"Slug of the target series, from get_series. Not its title or id."

First observedv2.0.0Aug 4, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false and openWorld=true, so the safety profile is covered. The description adds essentially nothing beyond them: no mention of required permissions, whether existing series ordering shifts when a position is inserted, or what a re-add of an already-member article does.

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, zero-waste phrase that communicates the core action immediately. It is perhaps too terse for a mutation tool, but nothing is padded or redundant.

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 three-parameter membership operation with full schema coverage and rich annotations, the essentials are present. What is missing is the effect on series ordering and any permission or idempotency behavior an agent would want to know before calling.

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%, so all three parameters including the optional 'position' with its append-if-omitted note are already documented. The description adds only the implication that 'article_slug' must reference a pre-existing article; otherwise it is baseline.

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?

Specific verb (add) plus resource (article) and target (series), which is enough to separate it from create_series and get_series. It is clear but never explicitly positions itself against those siblings.

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?

No guidance on when to use this versus create_series or get_series, and no prerequisites such as needing ownership of both the article and the series. The word 'existing' hints that the article must already exist, but that is inference rather than stated policy.

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