Skip to main content
Glama
Sign In
Medium Blog MCP Server

Medium Blog MCP Server

by Navneet1710
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Save Draft

save_draft

Save the generated blog content as a draft in the database for later editing or publishing.

Instructions

Save the generated blog draft to database

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>",
      "content": "<content>"
    },
    "name": "save_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesComplete blog content in markdown
session_idYesActive session ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

The description only states that it saves to a database, which implies a write operation, but it does not disclose whether existing drafts are overwritten, whether it is idempotent, what the return value is, or any failure conditions. No annotations are present to clarify this.

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 superfluous words. It follows a clear structure and gets straight to the point.

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 is adequate for a simple save operation but lacks details about the output schema (despite it being present) and does not cover edge cases such as invalid session IDs, duplicate saves, or error handling. This leaves some gaps in operational understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters are clearly described in the schema: session_id is the active session ID and content is the complete blog content in markdown. Schema coverage is 100% and descriptions are unambiguous, providing full semantic clarity.

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 action (save), object (generated blog draft), and destination (database). It is specific enough to distinguish it from outline-related tools, though it could explicitly mention it saves the full content draft.

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 is provided on when to use this tool versus alternatives like save_outline or generate_full_content. The description does not mention any precondition (e.g., content must be generated first) or relationship to other tools.

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