Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Substack publication posts

substack_publication_posts_list
Read-onlyIdempotent

Lists posts from a Substack publication archive with cursor pagination, sorting, and optional text or section filters for browsing or analyzing a publication's content.

Instructions

List the posts in a Substack publication archive. Requires publication. Returns a list (use cursor when paginated).

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 0 to 100,000; leave it at 0 and follow `page.nextCursor`. A page above 0 is refused with a 400 because the archive pages by cursor.
sortNoOrder. `oldest` is not supported.new
limitNoRows to return, 1 to 23.
queryNoOnly posts whose text matches this string.
cursorNoOpaque cursor from the previous page's `page.nextCursor`. Omit it for the first page.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
sectionNoOnly posts in this section id (from the publication's sections).
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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the required-parameter precondition and a cursor-paging note, but that paging detail is already spelled out far more thoroughly in the schema's `page` and `cursor` descriptions, so the marginal behavioral value is small.

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 sentences with the core purpose front-loaded and no filler. The 'Requires `publication`' clause is slightly redundant with the schema's required list, keeping it just under full marks.

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 10-parameter listing tool with no output schema, the description says only that a list is returned and mentions cursors; it does not characterize the post objects returned or note that page>0 is rejected. The rich schema compensates for most parameter gaps, but the return-value side is thin.

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%, including detailed notes on page limits, cursor format, sort enum exclusions, and publication identifier forms. The description repeats only the `publication` requirement and the cursor advice, adding nothing beyond the schema, so the baseline 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 with scope: 'List the posts in a Substack publication archive.' An agent immediately knows this enumerates archive posts. However, it gives no hint about how it differs from close siblings such as substack_publication_posts_search, substack_publication_posts_index_list, or substack_publication_posts_bodies_list.

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 line 'Requires `publication`' sets a precondition and 'use cursor when paginated' implies the paging pattern, but there is no explicit when-to-use or when-not-to-use guidance against the search/index/bodies siblings. Usage is only implied by the tool name.

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