Skip to main content
Glama
afikrim
by afikrim

create_post

Publish a post to your Medium profile by providing title, content in HTML or Markdown, optional tags, and choosing publish status. Optionally set canonical URL, notify followers, or select a license.

Instructions

Create a post on the authenticated user's Medium profile

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags to classify the post (max 3, max 25 chars each)
titleYesThe title of the post (max 100 chars for SEO, must also be in content body)
contentYesThe body of the post in HTML or Markdown format
licenseNoLicense for the post
author_idYesThe author's user ID (from get_profile)
canonical_urlNoOriginal home of this content if published elsewhere
content_formatYesFormat of the content: 'html' or 'markdown'
publish_statusNoPublish status: 'public', 'draft', or 'unlisted'
notify_followersNoWhether to notify followers of the publication
Behavior2/5

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

No annotations provided, and description only says 'Create a post', implying write behavior. Missing details on authentication, rate limits, or side effects.

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?

One concise sentence with zero wasted words. Front-loaded with key action and context.

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

Completeness2/5

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

With 9 parameters, 4 required, and no output schema, the description is too minimal. It doesn't explain how to obtain author_id, required content_format, or constraints like tags max 3.

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 baseline 3. Description adds no extra meaning beyond what the schema already provides.

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 verb 'Create' and resource 'post on authenticated user's Medium profile'. It distinguishes from sibling create_publication_post, which is for publications.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives like create_publication_post. No prerequisites or context provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/afikrim/medium-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server