Skip to main content
Glama
06ketan

medium-ops

by 06ketan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

publish_post

Publish a Medium story in markdown. Defaults to draft to avoid accidental publication; set publish_status to public or unlisted to publish. Supports tags, canonical URL, and dry-run.

Instructions

WRITE. Publish a story. content_format is markdown. Defaults to publish_status='draft' so nothing goes public by accident; set to 'public' or 'unlisted' to flip it. Uses the integration token and api.medium.com/v1/*. Dry-run by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
content_markdownYes
tagsNo
publication_idNo
publish_statusNodraft
canonical_urlNo
notify_followersNo
dry_runNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.1.2
    • addedInput schema / properties / canonical_url
      Added value: +{
+  "default": null,
+  "title": "Canonical Url",
+  "type": "string"
+}
    • addedInput schema / properties / content_markdown
      Added value: +{
+  "title": "Content Markdown",
+  "type": "string"
+}
    • addedInput schema / properties / dry_run
      Added value: +{
+  "default": true,
+  "title": "Dry Run",
+  "type": "boolean"
+}
    • removedInput schema / properties / kwargs
      Removed value: -{
-  "title": "Kwargs"
-}
    • addedInput schema / properties / notify_followers
      Added value: +{
+  "default": false,
+  "title": "Notify Followers",
+  "type": "boolean"
+}
    • addedInput schema / properties / publication_id
      Added value: +{
+  "default": null,
+  "title": "Publication Id",
+  "type": "string"
+}
    • addedInput schema / properties / publish_status
      Added value: +{
+  "default": "draft",
+  "title": "Publish Status",
+  "type": "string"
+}
    • addedInput schema / properties / tags
      Added value: +{
+  "default": null,
+  "items": {
+    "type": "string"
+  },
+  "title": "Tags",
+  "type": "array"
+}
    • addedInput schema / properties / title
      Added value: +{
+  "title": "Title",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "kwargs"
-]New value: +[
+  "title",
+  "content_markdown"
+]
    • changedInput schema / title
      Previous value: -"_toolArguments"New value: +"publish_postArguments"
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Discloses action type (WRITE), default draft status, dry-run behavior, and use of integration token. No output schema exists, but description hints at publish consequences. Lacks detail on what happens on success or side effects like follower notifications.

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?

Three short sentences, each valuable. Front-loaded with action and resource. No redundancy or fluff.

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?

Adequate for a complex tool with 8 parameters and no output schema. Missing explanation of return value or authentication requirements beyond 'uses integration token'. No reference to required fields (though in schema).

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?

With 0% schema description coverage, description adds meaning for content_format, publish_status options, and dry_run default. Does not explain tags, publication_id, canonical_url, or notify_followers, leaving half of 8 parameters undocumented.

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?

Description clearly states 'WRITE. Publish a story.' with specific verb and resource. Specifies content_format as markdown and distinguishes from sibling tools like 'clap_post' or 'post_response' by focusing on publishing.

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?

Explains default status behavior ('nothing goes public by accident') and how to override with 'public' or 'unlisted'. Mentions dry-run default but does not explicitly compare to other publish-related tools or list prerequisites like authentication.

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