Medium Blog MCP Server

Overview Schema Source Related Servers Discussions Admin

Export To Medium

export_to_medium

Convert blog content to Medium-ready markdown, bundling images, references, metadata, and a QA report for direct publication.

Instructions

Export blog to Medium-ready markdown format

Creates:

Medium-formatted markdown file
Images folder with all images
Citations/References section
Metadata JSON
QA Report

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": {
      "session_id": "<session_id>"
    },
    "name": "export_to_medium"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes	Active session ID

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The description indicates that files are created but does not disclose side effects such as whether existing files are overwritten, where outputs are stored, or whether any approval is required. With no annotations, this leaves important behavioral details unclear.

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 brief, well-structured, and free of unnecessary detail. The bullet list clearly communicates the tool's outputs without verbosity.

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?

The description covers the main purpose and output artifacts, but it lacks context about when the export should be performed, what the return value looks like, and any dependencies on prior steps. It is adequate for a simple tool but not fully self-contained.

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?

The only parameter, session_id, already has a clear schema description ('Active session ID'), so the description adds no additional semantic value. Schema coverage for parameters is effectively complete, meriting a baseline score.

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 clearly states the tool exports a blog to Medium-ready markdown and enumerates the created artifacts. It is specific about the resource and action, though it does not explicitly distinguish itself from the sibling get_export_files.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites such as an approved final draft. An agent would have to infer the appropriate context from the tool name alone.

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