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

medium-writer-mcp

by MuhammadAsher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_publication_stories

Read-onlyIdempotent

Retrieve recent stories from a Medium publication by slug, with an optional limit and full Markdown content for each story.

Instructions

Get the most recent stories from a Medium publication.

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": {
      "publication": "<publication>"
    },
    "name": "get_publication_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many stories to return (max 10).
publicationYesPublication slug from its URL, e.g. 'better-programming'.
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.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the description does not need to establish basic safety. It adds the useful behavioral detail that stories are 'most recent,' implying recency ordering. It does not discuss pagination, rate limits, or output-size behavior, though the schema covers the limit and content options.

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, front-loaded sentence with no unnecessary words. It is appropriately sized for a simple retrieval tool. Nothing is buried or repeated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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-only tool with full schema coverage and annotations, the description provides enough context to understand the core operation. It could add a little routing guidance against sibling retrieval tools, but it is otherwise complete. The lack of an output schema is offset by the schema's parameter documentation and the annotations.

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%, so each parameter is already documented in the schema. The description adds no parameter-specific meaning beyond what the schema provides. The baseline score of 3 is appropriate because the schema carries the parameter semantics.

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 uses a specific verb and resource: 'Get the most recent stories from a Medium publication.' This clearly identifies the operation and resource scope. It does not explicitly name sibling tools such as get_tag_stories or get_user_stories, so it stops short of full sibling differentiation.

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?

Usage is implied by the phrase 'from a Medium publication,' which suggests this tool is for publication-based story retrieval. However, the description does not state when to use it instead of get_tag_stories, get_user_stories, or other sibling retrieval tools. No exclusions or alternative-selection guidance are provided.

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