Skip to main content
Glama
mcp-public-intel

mcp-public-intel

by pecopeko

substack_public_posts

Fetch public Substack publication posts as clean Markdown, flag paywalled content without bypassing it, and optionally filter to free posts. No API key required.

Instructions

Fetch public Substack publication posts via /api/v1/archive and /feed RSS as clean Markdown, honestly flagging paywalled posts without bypassing paywalls. Zero API key required.

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_public_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of posts to return (1-30, default 10).
only_freeNoIf true, omit paywalled previews and return only free public posts.
publicationYesSubstack handle (e.g. 'pragmaticengineer'), subdomain, or custom domain URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose meaningful behavior: data sources with an apparent archive/RSS fallback, that paywalled posts are flagged rather than fetched, that no paywall bypass occurs, and that no auth is needed. It stops short of stating rate limits, pagination, or what happens for an invalid handle.

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?

A single front-loaded sentence that packs source, output format, paywall policy, and auth requirement with no filler. Slightly dense in one clause, but every element earns its place.

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 three-parameter read tool with full schema coverage and no output schema, the description supplies the essentials an agent needs: what it returns (Markdown), how paywalled content is handled, and that no key is required. Only error/edge behavior and result volume are left unstated.

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 all three parameters are already documented in the schema. The description's only added semantic is the paywall-flagging behavior, which loosely maps to only_free but adds no new constraints or formats beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Fetch public Substack publication posts') plus the exact endpoints used (/api/v1/archive and /feed RSS) and the output form (clean Markdown). An agent can distinguish this from feed/jobs/catalog siblings at a glance.

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?

Implied usage is clear from the description, and 'zero API key required' plus the paywall stance give useful preconditions, but there is no explicit when-to-use vs when-not guidance or named alternative for cases this tool cannot serve (e.g. private or paid content).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.