Skip to main content
Glama
Sign In
medium-writer-mcp

medium-writer-mcp

by MuhammadAsher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_user_stories

Read-onlyIdempotent

Retrieve a Medium author's recent stories, newest first, with optional full Markdown content for reading or export.

Instructions

Get the most recent stories by a Medium author (newest first).

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": {
      "username": "<username>"
    },
    "name": "get_user_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many stories to return (max 10).
usernameYesMedium username, with or without '@', e.g. 'asherazeem'.
include_contentNoInclude each story's full text as Markdown. Much longer output.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description's one added behavior is the 'newest first' ordering, which is genuinely useful. It says nothing about rate limiting, empty results for unknown authors, or whether the author is resolved by handle only.

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?

A single short sentence with zero filler, and the ordering detail is front-loaded in the parenthetical. Nothing is wasted.

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?

For a simple three-parameter read tool with full schema coverage and rich annotations, the description is serviceable. However, with no output schema it never indicates what a returned 'story' contains (title, URL, timestamps), which an agent would need to know before calling.

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?

Schema description coverage is 100%, including the limit maximum of 10 and the include_content cost warning, so the schema does the heavy lifting. The description adds no meaning beyond it; it does not even echo that the result count is capped. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Get the most recent stories') plus scope ('by a Medium author') and ordering ('newest first'). It is clear what it does, but it never distinguishes itself from siblings like get_publication_stories or get_tag_stories, even though those retrieve the same resource through a different filter.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'by a Medium author' phrasing implies the selection condition, but there is no explicit when-to-use or when-not, and no named alternative for publication- or tag-scoped retrieval. An agent must infer the routing choice from sibling names alone.

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