Misar.Blog MCP Server

List my series

get_series

Read-onlyIdempotent

List every series the authenticated account owns. Despite the name this returns the whole collection, not one series — there is no single-series lookup.

Use it to find a series slug before calling add_to_series, or to check whether a series already exists before create_series makes a duplicate.

Reads only; nothing is created or modified. Requires an API key, and takes no parameters — it is unfiltered and unpaginated. Returns { series, total } where each entry carries id, slug, title, description, url and article_count. An empty list means the account has no series yet, which is not an error.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark readOnlyHint true, but the description adds crucial behavioral details beyond that: it notes API key requirement, no parameters, unfiltered and unpaginated behavior, return shape ({ series, total } with specific fields), and that an empty list is valid, not an error. This fully discloses side effects and expectations.

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?

The description is concise yet packed with information, structured in short paragraphs. The first sentence states purpose, the second covers usage, and the third details behavior and return format. Every sentence adds unique value with no redundancy.

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?

For a simple list-all tool with no parameters, the description covers all necessary context: authentication, return shape with field names, handling of empty results, and typical use cases. It is complete without needing an output schema.

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?

With zero parameters and 100% schema coverage, the baseline is 4. The description reinforces the absence of parameters and clarifies the unfiltered/unpaginated nature, adding context that is essential for correct usage.

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 the tool lists every series owned by the authenticated account, and explicitly clarifies that despite the name it returns the whole collection, not a single series. This distinguishes it from sibling tools like get_article and list_my_articles.

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?

It gives explicit, actionable usage guidance: use it to find a series slug before calling add_to_series, or to check for duplicates before create_series. These alternatives are named and the context is clear, making the when-to-use unambiguous.

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 tools Inspect

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.1/5.0

Disambiguation4/5

The tools mostly map to clearly distinct resources and actions, with good behavioral separation between create_draft, publish_article, and update_article, and between the two title-generating tools. Some naming choices are still slightly misleading, such as get_series returning the full collection rather than a single series, and generate_cover_image references a non-existent upload_image tool.

Naming Consistency4/5

The vast majority of tools follow a clean lowercase verb_noun pattern, including create_*, get_*, list_*, and add_* names. Notable exceptions are upgrade, a bare verb that also mixes read and mutate behaviors, and get_series, which functions more like a list than a get.

Tool Count3/5

23 tools is in the heavy range for an MCP server, exceeding the ideal 3-15 span. That said, the tools do span legitimate blogging concerns such as articles, reactions, series, newsletters, analytics, and AI assistance, so the count feels broad rather than padded.

Completeness2/5

The surface covers article creation, reading, updating, and publishing, but there is no delete or unpublish for articles/drafts, no way to remove an article from a series, and no update/delete for series. The dangling reference to upload_image in generate_cover_image also suggests a missing tool, and agents will hit dead ends trying to undo publication or remove content.

Resources

Need Help?