Skip to main content
Glama
Sign In
MisarBlog MCP Server

MisarBlog MCP Server

by Misar-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create draft

create_draft

Save an article as a draft on Misar.Blog so you can review and edit it before publishing. Provide a title, Markdown body, and optional tags to stage content for approval.

Instructions

Save an article as a draft on Misar.Blog (for review before publishing)

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

Input Schema

NameRequiredDescriptionDefault
tagsNoTags for the draft
titleYesDraft title
body_markdownYesFull article body in Markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed3 schema fields changedv5.1.3
    • changedInput schema / properties / body_markdown / description
      Previous value: -"Article body so far, as Markdown."New value: +"Full article body in Markdown"
    • changedInput schema / properties / tags / description
      Previous value: -"Topic tags to carry through to publication."New value: +"Tags for the draft"
    • changedInput schema / properties / title / description
      Previous value: -"Working headline. Can be changed before publishing."New value: +"Draft title"
  3. Changed3 schema fields changedv5.1.0
    • changedInput schema / properties / body_markdown / description
      Previous value: -"Full article body in Markdown"New value: +"Article body so far, as Markdown."
    • changedInput schema / properties / tags / description
      Previous value: -"Tags for the draft"New value: +"Topic tags to carry through to publication."
    • changedInput schema / properties / title / description
      Previous value: -"Draft title"New value: +"Working headline. Can be changed before publishing."
  4. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, open-world write, so the safety profile is covered. The description adds only that the draft is intended for review prior to publishing, which clarifies visibility state but says nothing about authentication, duplicate behavior on repeat calls, or whether drafts are private.

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?

One front-loaded sentence with no filler; the action and intended use come first. The parenthetical is slightly compressed but earns its place by signaling the review workflow.

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 create tool with full schema coverage and annotations covering safety, not much is missing. However, it does not say what comes back (e.g. a draft ID or URL) or how this connects to publish_article and update_article, which an agent needs to continue the 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 description coverage is 100% with all three parameters documented, so the schema carries the parameter burden. The description adds no format hints (e.g. Markdown expectations, tag limits) beyond what the schema already states, making the baseline 3 appropriate.

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?

"Save an article as a draft" gives a specific verb and resource, and naming Misar.Blog scopes it to the platform. It implicitly separates itself from publish_article by framing the result as a draft, though it never names that sibling explicitly.

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

Usage Guidelines3/5

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

The parenthetical "for review before publishing" implies the workflow position (create first, publish later), which is useful. It stops short of naming publish_article or update_article as the next step, and gives no exclusions or prerequisites.

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