Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

medium_user_posts

Fetch a Medium author's public posts by username to review their feed; optionally set cache freshness for repeat requests.

Instructions

medium: User posts. GET /v1/medium/user/posts. Posts in an author's public feed. An empty feed costs 0 credits. Costs 1 credit when it succeeds. Costs 0 credits when posts is empty. 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>"
    },
    "name": "medium_user_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

C2.9/5.0
Behavior3/5

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

With no annotations, the description does carry real behavioral weight by disclosing the credit model in unusual detail (free on empty, 1 credit on success, free on errors/cache hits). However, it says nothing about pagination, result ordering, result size, or whether the read requires auth, and the final sentence defers cost to an unspecified 'published cost', which softens the earlier promises.

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

Conciseness2/5

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

The opening is well front-loaded, but roughly two-thirds of the text is credit boilerplate that repeats itself: 'An empty feed costs 0 credits' and 'Costs 0 credits when posts is empty' say the same thing, and the trailing sentence about not-found/empty charging partially undercuts them.

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 two-parameter read with no output schema, an agent still lacks basics: what a returned post contains, whether results are paginated or capped, and what an empty feed looks like structurally. The cost picture is complete, but the call/response picture is not.

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 both parameters (username, cache_max_age) are already documented, including the '@'-free format. The description only restates the cache-hit cost implication for cache_max_age and adds nothing about username semantics, so baseline 3 applies.

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 concrete verb+resource (user posts / posts in an author's public feed) and pins it to an endpoint (GET /v1/medium/user/posts). The platform scope is clear from the name and text, though it never explicitly contrasts itself with the many sibling *_user_posts tools.

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?

There is no when-to-use guidance at all: nothing says to pick this over medium_article or bluesky_user_posts, no prerequisite about resolving a username first, and no note on when caching is worth enabling beyond a one-line cost hint. The only selection-adjacent content is pricing.

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