Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Substack post comments

substack_post_comments_list
Read-onlyIdempotent

Fetch the full nested comment tree for a Substack post by URL or numeric ID, with optional sorting by best, oldest, or newest, and return it as a list.

Instructions

Get the whole nested comment tree of a Substack post. Requires post. Returns a list.

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": {
      "post": "<post>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "substack_post_comments_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
postYesRequired. A post: its numeric id (`223208969`) or its URL (`https://www.astralcodexten.com/p/...`). Post comments need the URL form.
sortNoComment order. The whole tree is returned either way.best
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.
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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds the useful behavioral fact that the entire tree comes back in one call, but 'Returns a list' sits awkwardly against 'nested comment tree' and gives no sense of depth, size, or pagination limits.

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 with the core capability front-loaded and no filler. The closing 'Returns a list.' is low-information and slightly conflicts in register with 'nested comment tree', but it costs little.

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?

With no output schema, the description carries the burden of describing the return value, and 'a list' is too thin for a nested comment tree whose depth and shape the caller cannot otherwise infer. It also omits the pagination/volume picture for a tool that could return a very large tree.

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 the important detail that comment listing requires the URL form of `post` and that `sort` does not truncate the tree, so the baseline of 3 applies. The description's mention of `post` merely repeats what the schema already documents.

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 the whole nested comment tree of a Substack post') and flags that the result is nested rather than flat, which separates it from list-style siblings like substack_note_replies_list. It stops short of naming which sibling tool to use when a caller wants something other than the full tree.

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 `post`', which is a requirement, not a when-to-use rule. There is no mention of when to prefer this over substack_post_get, substack_note_replies_list, or the per-platform *_post_comments_list tools, and no exclusions or prerequisite context.

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