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

medium-writer-mcp

by MuhammadAsher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

open_in_medium

Copies formatted article text to the clipboard and opens a new Medium story in your browser for pasting; no login automation or publishing.

Instructions

Copy the article to the clipboard as formatted text and open a new Medium story (macOS).

No login or browser automation: it opens medium.com/new-story in the user's normal browser, where they're already signed in, and they press Cmd+V. Replaces whatever is on the clipboard. Show the user the warnings, and the tags/subtitle to enter in Medium's publish dialog. Nothing is published.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "open_in_medium"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoUp to 5 tags (entered in Medium's publish dialog).
titleNoStory title. Defaults to the first '# ' heading.
browserNomacOS app to open, e.g. 'Safari' or 'Google Chrome', or 'default'. Defaults to $MEDIUM_BROWSER, else Safari.
markdownNoArticle Markdown, if there is no file.
subtitleNoOne-line subtitle shown under the title.
file_pathNoPath to the article's .md file. Use this or `markdown`.
canonical_urlNoOriginal URL if cross-posting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses the real side effect that matters: the clipboard is overwritten, so the agent should warn the user before calling the tool. It also states that nothing is published and that the browser opens to medium.com/new-story, so the agent knows the real effect is only in the user's normal browser and that manual steps follow.

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?

The description is three short sentences, front-loaded with the action and immediately followed by the constraint that no automation occurs. The final sentence ('Show the user the warnings, and the tags/subtitle...') is slightly awkward in wording and mixes agent instructions into the tool description, but it is not wasteful.

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?

For a seven-parameter tool with all optional arguments and no output schema, the description covers the important unknowns: what gets modified, what the user must do next, and that no publish occurs. It stops short of describing what the tool returns to the agent (warnings, ready-to-paste values), leaving the return shape only implied.

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 seven parameters (tags, title, subtitle, browser, markdown, file_path, canonical_url) already carry their own descriptions. The description adds only a little meaning beyond that: it says the tags and subtitle are entered into Medium's publish dialog, which clarifies their downstream use rather than their format.

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 names a concrete verb pair (copy to clipboard, open a new Medium story) plus a specific platform (macOS), so an agent knows exactly what the tool accomplishes. It is clearly distinguishable from the read/export/prepare siblings, which do not mutate the clipboard or launch a browser.

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

Usage Guidelines4/5

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

It gives clear conditions of use: no login or browser automation is needed, and the user must paste manually, which tells the agent this is a handoff-to-user flow rather than an automated publish. It does not name a sibling alternative (e.g. export_article vs prepare_article vs open_in_medium), so there is no explicit when-not guidance.

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