Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

substack_note_restacks

Fetch the Substack Notes that restacked a given Note, including each restack's commentary, with cursor-based pagination for additional pages.

Instructions

List the Notes that restacked a Substack Note. Returns one page of the Notes that restacked a given Note, each in the same shape as the single-Note endpoint. A restack may carry its own commentary in body or be a bare reshare with an empty body. Pagination is cursor-based.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoOpaque cursor from a previous response's next_cursor
note_idYesNumeric Note id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that the result is one page, that each item matches the single-Note shape, and that restacks can have a body or be bare (empty body). It also states cursor-based pagination. This goes beyond the schema and covers core behavioral aspects, though it does not mention auth or error conditions.

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

Conciseness5/5

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

The description is two sentences, front-loaded with the primary action followed by compact details about output shape, body semantics, and pagination. Every sentence conveys necessary information without redundancy.

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?

The tool is a simple list endpoint with two well-described parameters. The description explains the return shape (same as single-Note endpoint), the meaning of an empty body, and pagination behavior. There is no output schema, but the description fills the critical gaps for correct invocation.

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?

The schema already documents both parameters (note_id, cursor) with clear descriptions at 100% coverage. The description adds only indirect references ('given Note' and 'cursor-based') without providing new semantic detail. Baseline of 3 is appropriate given the schema's completeness.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'List the Notes that restacked a Substack Note.' It also clarifies scope with 'Returns one page' and contrasts the output shape with the single-Note endpoint. There is no ambiguity about what action this tool performs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use it, i.e., when you have a note_id and want to see the Notes that restacked it. It also mentions cursor-based pagination, indicating how to retrieve additional pages. It does not explicitly name alternatives or exclusion scenarios, but the context is clear.

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