Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Substack note restacks

substack_note_restacks_list
Read-onlyIdempotent

Lists the Substack notes that restacked a given note using its noteId, with cursor pagination for browsing all restacks.

Instructions

List the notes that restacked a Substack note. Requires noteId. 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": {
      "noteId": "<noteId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "substack_note_restacks_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque cursor from the previous page's `nextCursor`.
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds only the pagination behavior ('use cursor when paginated'), and says nothing about ordering, page size, or what an empty result means.

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 purpose front-loaded and no filler. The parenthetical pagination note is slightly compressed in phrasing but still earns its place.

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 annotations and a fully documented schema, the description is adequate for a simple read-only list tool. However, it omits any mention of the required conversation_id handshake or the context/llm_model analytics parameters, which are operationally significant for first-call sequencing.

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%, so all five parameters, including cursor and noteId, are documented in the schema itself. The description restates the noteId requirement and the cursor's purpose without adding format or usage detail beyond the schema, 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?

The description names a specific verb and resource: 'List the notes that restacked a Substack note.' That is clearly distinct from post-level restackers or note replies, though it never names those siblings explicitly, so an agent must infer the boundary from the word 'note'.

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 or when-not-to-use guidance. The only constraint is 'Requires `noteId`', which is already enforced by the schema; nothing tells the agent when to prefer this over substack_note_replies_list or substack_post_restackers_list.

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