Skip to main content
Glama
Sign In
Substack MCP Server

Substack MCP Server

by cotletdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get feed

get_feed
Read-onlyIdempotent

Fetch a page of your Substack home feed split into posts and Notes, choosing the For You or Following tab and passing next_cursor to continue.

Instructions

Your Substack home feed: posts and Notes, For you or Following.

Returns one page of the home feed of the Substack app, split into posts and Notes in feed order. for_you is Substack's own mix; following holds only people and publications you follow or subscribe to. Suggestions of people to follow are left out. Reading marks nothing seen. Page with next_cursor; the feed is personal and changes between calls.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNofor_you (Substack's picks) or following (whom you follow). Default: for_you.
cursorNonext_cursor from the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, yet the description adds non-obvious behavior: reading marks nothing seen, suggestions are omitted, and the feed is personal and changes between calls. That is real value beyond the structured fields; only the shape of returned items is left unstated.

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

Conciseness5/5

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

Four short sentences, front-loaded with what the feed is, followed by mode semantics, exclusions, and pagination. Nothing is repeated and every sentence carries information.

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?

There is no output schema, and the description covers the return split (posts and Notes in feed order), pagination, and the personal/ephemeral nature of results. Only the concrete item structure is unspecified, which is a minor gap for a read tool with full annotation coverage.

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 both parameters are already documented. The description restates the tab semantics (Substack's mix vs. whom you follow) and pagination via next_cursor, adding only marginal meaning over the schema, so baseline 3 applies.

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?

The first line names a specific resource (Substack home feed) and its contents (posts and Notes) plus the two modes, so an agent can distinguish it from list_posts, list_notes, or search_substack without opening the schema.

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?

The description explains what for_you and following each contain and that suggestions are excluded, which shapes selection, but it never states when to prefer this tool over siblings like list_notes or list_posts. Usage is implied rather than prescribed.

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