Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Substack publication feed

substack_publication_feed_get
Read-onlyIdempotent

Fetches a Substack publication's feed and its recent items so you can inspect or summarize posts by publication ID, subdomain, host, or URL. Requires a publication identifier.

Instructions

Get a Substack publication's feed with its newest items. Requires publication.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "substack_publication_feed_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
publicationYesRequired. A publication: its numeric id (`89120`), its Substack subdomain (`astralcodexten`), its host (`www.astralcodexten.com`) or its URL. A numeric id is refused with a 400 on the routes that need a subdomain, host or URL.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered structurally. The description adds only the ordering trait ("newest items"), leaving open how many items are returned, whether the feed is limited by window, and how publication identifiers behave across routes.

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?

Two short, front-loaded sentences with no filler, and the ordering semantics appear immediately after the resource. The second sentence largely duplicates the schema's required-fields signal, which is a small waste.

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 read tool with full schema coverage and no output schema, the minimum is met, but "feed" is left undefined relative to the several posts-listing siblings, and nothing tells the agent how large or how fresh the returned feed will be. The unused conversation_id/concurrency contract is also unmentioned.

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% and the publication parameter's id/subdomain/host/URL forms and the numeric-id rejection are already documented in the schema. The description adds nothing beyond repeating that `publication` is required, so the baseline of 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?

States a specific verb and resource ("Get a Substack publication's feed") and adds scope ("with its newest items"), so the agent knows this is a feed read rather than a search. However, it never distinguishes the feed from nearby siblings like substack_publication_posts_list or substack_publication_posts_index_list, so the agent must guess which one returns the feed.

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?

The only guidance is "Requires `publication`", which restates a schema requirement rather than explaining when to choose this tool. There is no mention of when a feed is preferable to a posts list, no pagination or recency caveats, and no exclusions.

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