Medium Blog MCP Server

Overview Schema Source Related Servers Discussions Admin

Create Blog Session

create_blog_session

Start a blog writing session by providing a topic and target length to automate research, content generation, quality checks, and Medium export for technical posts.

Instructions

Start a new blog writing session

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": {
      "topic": "<topic>"
    },
    "name": "create_blog_session"
  }
}

Input Schema

Name	Required	Description	Default
`topic`	Yes	Blog topic (e.g., "Latest advancements in LLMs")
`target_length`	No	short (800-1200), medium (1500-2500), long (3000+)	medium

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?

With no annotations to cover safety or side effects, the description carries the full burden. 'Start' implies creation but does not disclose potential consequences, such as whether a session is persisted, whether any initial data is required, or what happens on conflict. The description lacks any behavioral detail beyond the act of starting.

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 a single, concise sentence with no filler words. It is perfectly sized for the tool's purpose and contains only the essential action, making it highly efficient.

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?

Even though the tool is simple, its position in a complex workflow (involving research, outline, and export) suggests that a mention of the session ID or next steps would be valuable. The description omits any reference to return values or how the session integrates with subsequent tools, leaving the agent without important contextual information.

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 input schema provides descriptions for both parameters (topic and target_length), including examples and length ranges, so schema coverage is 100%. The tool description itself adds no additional meaning beyond the schema, matching the baseline score of 3.

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 'Start a new blog writing session' uses a clear verb and resource, distinguishing it from sibling tools like get_session_status and list_sessions. However, it is somewhat generic as it doesn't clarify what a session entails or what the tool's specific role in the workflow is, so it falls short of a 5.

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?

The description gives no explicit guidance on when to use this tool versus alternatives. While the name and sibling context imply it should be used to initiate a new session, the description itself does not state any such condition or contrast with other tools, leaving usage to inference.

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