Crawlora MCP

substack_note_restacks

Read-only

List the Notes that restacked a given Substack Note, each in the same shape as substack_note. A restack may carry its own commentary or be a bare reshare with an empty body. Cursor-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": {
      "note_id": "<note_id>"
    },
    "name": "substack_note_restacks"
  }
}

Input Schema

Name	Required	Description	Default
`cursor`	No	Opaque cursor from a previous response's next_cursor.
`note_id`	Yes	Required numeric Note id.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the read-only and open-world profile, but the description adds real behavioral context: return objects match substack_note's shape, restacks may be bare reshares with empty bodies, and results are cursor-paginated. The empty-body caveat is exactly the kind of edge case an agent needs to parse output correctly.

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?

Three tight sentences, front-loaded with the core action, followed by the data-shape caveat and pagination note. No redundancy or filler.

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?

An output schema exists, so return values need not be re-explained; annotations carry the safety profile; schema documents both params. The description supplies the remaining behavioral nuance (shape parity, empty-body restsacks, pagination), leaving nothing an agent needs missing.

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 the schema already documents both note_id and cursor. The description only reiterates cursor-pagination without adding format, limits, or cursor-usage detail, so the baseline 3 is appropriate.

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?

States a concrete verb (List) and a precise resource (Notes that restacked a given Note), which an agent can distinguish from the sibling substack_note_replies. Scope is unambiguous: restacks of one note, not replies or the note itself.

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?

The purpose implies when to reach for it (listing restacks of a note), but there is no explicit routing guidance versus alternatives like substack_note_replies or substack_notes, and no stated preconditions for obtaining a valid note_id. Usage is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?