Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

substack_post

Retrieve a public Substack post by publication hostname and slug, enabling article access for research, monitoring, or archiving.

Instructions

substack: Post. GET /v1/substack/post. One public post by publication and slug. 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": {
      "publication": "<publication>",
      "slug": "<slug>"
    },
    "name": "substack_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesPost slug.
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
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does well on the cost model: 1 credit on success, free for errors, blocked/timed-out requests, invalid requests and cache hits. It leaves out other behavior an agent needs — auth requirements, rate limits, and whether the response is full text or metadata — so the disclosure is real but partial.

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

Conciseness4/5

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

The scope sentence is front-loaded and the cost rules follow in a compact block. The leading 'substack: Post. GET /v1/substack/post.' restates the name and endpoint with little added value, but the rest is dense with information rather than padding.

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 three-parameter read with no output schema, the description covers scope and the credit accounting model thoroughly. It stops short of describing what is returned (full post body versus metadata) or any access constraints, which an agent would want before invoking.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all three parameters are documented structurally, and the description reinforces the publication/slug lookup while noting that a cache hit via cache_max_age costs 0 credits. That cache-cost linkage adds meaning beyond the schema's own wording.

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 states a specific resource and scope: 'One public post by publication and slug', with the endpoint path as backup. The singular 'post' versus the sibling 'substack_posts' implies a single-item fetch, but the description never names that sibling to make the distinction 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 by the phrase 'One public post by publication and slug' — an agent can infer this is the single-post lookup rather than a listing. There is no explicit guidance on when to prefer this over substack_posts, nor any stated prerequisites such as whether the post 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