Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Substack posts with bodies

substack_publication_posts_bodies_list
Read-onlyIdempotent

Retrieve posts from a Substack publication with their full free article bodies, using a cursor to page through results when needed.

Instructions

List Substack posts with their full free bodies. 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_bodies_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPosts to return, 1 to 50.
cursorNoOpaque cursor from the previous page's `nextCursor`.
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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and open-world, so the safety bar is low. The description still adds real value by disclosing that only 'free' bodies are returned (paid content is stripped) and that responses may be paginated via cursor.

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?

Three short sentences, front-loaded with the core action and scope. 'Requires publication' largely repeats the schema's required list and the cursor note is near-redundant, but nothing is bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with full schema coverage, annotations, and no output schema, the description covers what an agent needs: the resource, the free-body scope, the required input, and pagination behavior. The analytics/plumbing params are adequately documented in the schema itself.

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 every parameter including cursor, limit and publication is already documented in the schema. The description only reiterates that publication is required and that cursor handles pagination, adding no syntax or format detail beyond the schema.

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?

Specific verb and resource: 'List Substack posts with their full free bodies.' The word 'bodies' distinguishes it implicitly from the plain posts-list sibling, and 'free' flags the paywall limitation, but no sibling is named 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?

Provides a prerequisite ('Requires publication') and a pagination hint ('use cursor when paginated'), but never says when to prefer this over substack_publication_posts_list or substack_publication_posts_index_list. Usage is only implied by the word 'bodies'.

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