Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

substack_posts

Retrieve recent public posts from a publication by hostname or name.substack.com via the Fetchproof API.

Instructions

substack: Publication posts. GET /v1/substack/posts. Latest public posts on a publication. Pass a hostname, or a name that lives at name.substack.com. An empty page 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": {
      "publication": "<publication>"
    },
    "name": "substack_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
publicationYesPublication hostname.
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.5/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 disclose the credit economics in detail: empty page 0 credits, successful call 1 credit, errors/blocked/timeouts/invalid/cache hits free. It still omits pagination behavior, auth requirements, and rate limits, so it is strong but not complete.

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?

Front-loaded and mostly efficient, but the credit-cost material is repetitive: 'An empty page costs 0 credits' and 'Costs 0 credits when posts is empty' say the same thing, and the final sentence about not-found results is convoluted.

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?

There is no output schema, so the description should say something about the shape of returned posts and pagination; it says nothing about either. The cost model is well covered, but return-value expectations for a list endpoint remain unset.

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 coverage is 100%, so the schema already documents both parameters including the cache_max_age zero-cost hint. The description adds only the hostname-or-name.substack.com shorthand for the publication value, which is a modest clarification rather than new 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?

States a specific verb and resource: 'Latest public posts on a publication' plus the backing route GET /v1/substack/posts. It is distinguishable from the singular substack_post sibling by the word 'posts' and 'Latest,' but it never names that sibling, so the differentiation is implicit rather than explicit.

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 only implied: the agent infers 'use this to list a publication's posts.' No when-not-to-use guidance, no mention of substack_post for single posts, and no prerequisites such as whether the publication must be public.

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