Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

medium_article

Retrieve a specific Medium article's full text from an author's public feed using the username and article ID.

Instructions

medium: Article. GET /v1/medium/article. One article from the author's public feed, including its text. An article that has left the feed is not found. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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

Input Schema

NameRequiredDescriptionDefault
idYesArticle id from the feed.
usernameYesMedium username, without @.
cache_max_ageNoServe a cached response when it is newer than this. A cache hit costs 0 credits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses the credit cost on success, that errors/blocked/timed-out/invalid requests and cache hits are free, and the not-found failure mode. It stops short of auth requirements, rate limits, or whether paywalled/private articles return partial text.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is correctly front-loaded, but roughly half the text is billing boilerplate, and the closing clause ("charged only where that operation's published cost says so") is circular and adds little. It is dense rather than padded, but the pricing prose could be tightened.

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 two-required-parameter read with no output schema, the description covers purpose, identity inputs, cost model, and the main failure mode, which is enough to call it correctly. Remaining gaps (response shape, auth, paywalled content behavior) are modest for this complexity level.

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 id, username, and cache_max_age are already documented in the schema; baseline 3 applies. The description adds only marginal meaning, chiefly reinforcing that a cache hit is free and that the returned article includes its text.

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 names a specific verb+resource: fetch "one article from the author's public feed, including its text," which is far more concrete than a restated title. It implicitly contrasts with list-style siblings such as medium_user_posts by stressing a single article, but never names an alternative, so the differentiation is only partial.

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?

There is one real usage constraint: an article that has left the feed is not found, which tells the agent this tool cannot retrieve removed/archived content. However, no positive when-to-use framing or explicit pointer to a sibling (e.g., listing an author's posts first) is given, so the agent must infer the routing.

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