Medium Blog MCP Server

Overview Schema Source Related Servers Discussions Admin

Approve Outline

approve_outline

Approve a generated outline to proceed with content generation in the Medium Blog MCP server. Use this tool after reviewing an outline to confirm and move to the next step.

Instructions

⭐ USER APPROVES outline to proceed with content generation

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

Input Schema

Name	Required	Description	Default
`session_id`	Yes	Active session ID

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

There are no annotations, so the description carries the transparency burden. It discloses the main side effect—proceeding to content generation—but does not mention whether the action is reversible, whether it changes session state, or what happens if called more than once.

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, direct sentence with no filler. The emoji and capitalization draw attention to the key action without adding unnecessary length.

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 confirmation action, but it omits what the tool returns and any preconditions (e.g., the outline must exist and be generated first). Given the lack of annotations and output schema details, some context is missing.

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 only parameter, session_id, is fully covered by the schema description as 'Active session ID'. The tool description does not add any additional semantics, so it stays at the baseline.

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 clearly states the tool's purpose: approving an outline to move forward with content generation. It also distinguishes this from related approval tools like approve_research and approve_final_draft by naming the outline and the next stage.

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?

The description implies that the tool should be called when the user approves the outline and wants content generation to proceed. It does not explicitly contrast with sibling approval tools, but the phrase 'outline' and 'content generation' provide enough context to select it.

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