Medium Blog MCP Server

by Navneet1710

Overview Schema Source Related Servers Discussions Admin

Python

Local

Modify Outline

modify_outline

Update blog post outlines by modifying titles, sections, and structure for a given session.

Instructions

Modify outline sections, titles, or structure

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

Input Schema

Name	Required	Description	Default
`session_id`	Yes	Active session ID
`modifications`	Yes	Dictionary with changes to make { "title": "new title", "subtitle": "new subtitle", "sections": { "2": {"name": "new name", "key_points": [...], "target_words": 800} }, "add_section": {"order": 4, "name": "...", "key_points": [...], "target_words": 500}, "remove_section": 3 }

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose side effects such as whether changes are persisted, whether the outline's approval status is affected, or whether validation is performed. The agent is left to infer these behaviors from context.

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 exceptionally concise, containing only the essential verb, object, and scope. No filler or redundant content exists, and the structure is straightforward.

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?

Given the rich set of sibling tools, the description lacks contextual information about how this tool fits into the overall workflow. However, the schema is self-explanatory for basic modifications, so it is not severely incomplete.

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 100% coverage of parameters, including a detailed example for the 'modifications' object. The description adds a useful example of the nested structure, but does not clarify semantics for each field (e.g., required keys within nested objects or how 'remove_section' is keyed).

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 verb 'Modify' and the resource 'outline', and specifies the scope: sections, titles, or structure. It distinguishes the tool from related outline tools like generate_outline and save_outline, though it could be more specific about the expected outcome.

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 provides no explicit guidance on when to use this tool versus alternatives like generate_outline or approve_outline. It does not mention prerequisites (e.g., an existing outline must be present) or the intended stage in the workflow.

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