Skip to main content
Glama
Sign In
medium-writer-mcp

medium-writer-mcp

by MuhammadAsher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

prepare_article

Read-onlyIdempotent

Checks Markdown for Medium compatibility, cleans supported formatting, flags unfixable issues, and returns word count and reading time for paste-ready drafts.

Instructions

Check Markdown against what Medium supports and return a cleaned version.

Converts tables to aligned text, demotes extra/deep headings, turns checklists into emoji, and reports anything it can't fix (nested lists, footnotes, raw HTML, missing alt text, title length, tags). Also returns word count and reading time.

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": {
      "markdown": "<markdown>"
    },
    "name": "prepare_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoUp to 5 tags.
titleNoStory title. Defaults to the first '# ' heading.
markdownYesThe article body in Markdown.
subtitleNoOne-line subtitle shown under the title.
canonical_urlNoOriginal URL if this was first published elsewhere (protects SEO).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so safety is covered; the description adds real value by disclosing the concrete rewrites performed and the class of unfixable issues it merely reports (nested lists, footnotes, raw HTML, alt text). It does not explicitly state that nothing is published or persisted, which is the one thing an agent might still wonder about given the 'prepare' name.

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?

Two sentences, purpose front-loaded, and the transformation list is dense but each item earns its place. The middle sentence is a long run-on enumerating five issue types, which slightly hurts scannability.

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

Completeness4/5

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

With no output schema, the description usefully declares what comes back: a cleaned Markdown version, an issue report, word count, and reading time. It stops short of saying how issues and the cleaned text are packaged (separate fields vs. inline), which is the remaining gap for a tool with five parameters.

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%, so all five parameters are already documented in the schema, including the title-defaults-to-first-heading rule. The description only indirectly touches parameters via 'title length, tags', adding marginal meaning beyond what is already structured, so the 3 baseline applies.

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?

Names a specific verb+resource: 'Check Markdown against what Medium supports and return a cleaned version.' It also enumerates the exact transformations (tables, headings, checklists) and the diagnostics returned, so an agent can tell this is a pre-publication sanitizer rather than the publish/export siblings.

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?

Usage is only implied: the phrase 'against what Medium supports' suggests running this before any Medium submission, but there is no explicit when-to-use, when-not-to-use, or named alternative. No prerequisites or ordering relative to export/publish siblings are stated.

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