Medium Blog MCP Server

by Navneet1710

Overview Schema Source Related Servers Discussions Admin

Python

Local

Add Custom Source

add_custom_source

Add a custom source URL to the active session for content research and generation.

Instructions

Add additional source manually

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Source URL to fetch
`session_id`	Yes	Active session ID
`source_type`	No	Type of source (web, pdf, image)	web

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

C2.3/5.0

Behavior1/5

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

The description does not disclose any behavioral traits such as side effects, permission requirements, or the meaning of 'manually'. With no annotations, the description is the sole source of behavioral information and is insufficient.

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 redundant words or elaboration, making it perfectly 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?

The description omits essential context about what a 'source' is, how it relates to the session, and what the expected outcome or output is. Although an output schema exists, it is not referenced, and the description alone leaves an agent uncertain about the tool's role.

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 already provides descriptions for all three parameters (url, session_id, source_type), achieving 100% coverage. The description adds no extra meaning beyond the schema, so per the rubric, baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Add additional source manually' states a verb and object, but 'source' is ambiguous without context. It doesn't specify what kind of source or its role in the session, which is less specific than the example in the calibration.

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

Usage Guidelines1/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, nor on prerequisites or conditions. The description is purely declarative and offers no decision support.

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