Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Substack note replies

substack_note_replies_list
Read-onlyIdempotent

List reply branches and comments for a Substack note using its note ID to inspect discussion threads and responses.

Instructions

List the reply branches and comments of a Substack note. Requires noteId. 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": {
      "noteId": "<noteId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "substack_note_replies_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteIdYesRequired. A note id as Substack displays it, e.g. `378007586`.
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

C2.9/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 only the mild structural hint that replies are organized into 'branches' with 'comments'. It says nothing about pagination, ordering, depth of nesting, or whether the call requires auth or a subscription.

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

Conciseness3/5

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

It is short and front-loaded, which is good, but two of the three sentences carry little weight: 'Requires `noteId`' duplicates the schema and 'Returns a list' is near-vacuous. Tightening to one sentence about the reply-branch structure would lose nothing.

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

Completeness2/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 must characterize the return value, and 'Returns a list' does not say what a list element is or whether branches nest comments. For a read tool whose payload structure is the main unknown, this leaves a real gap even though annotations cover safety.

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 a concrete example note id, so the schema does the work and baseline 3 applies. The description's 'Requires `noteId`' merely restates the required field without adding format or constraint 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?

The description states a specific verb and resource: 'List the reply branches and comments of a Substack note.' This clearly separates it from single-object reads like substack_note_get and from explore/list-of-notes tools. It stops short of naming a sibling, so it does not reach full differentiation.

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?

There is no when-to-use framing at all — nothing tells the agent when to prefer this over substack_note_get or substack_post_comments_list. The only conditional information is 'Requires `noteId`', which is a prerequisite already enforced by the schema's required array.

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