Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

substack_note_replies

Fetch public replies to a Substack Note using its numeric ID. Returns one page of replies with cursor-based pagination.

Instructions

List replies to a Substack Note. Returns one page of public replies to a Note, each in the same shape as /substack/note. Pagination is cursor-based: pass the previous response's next_cursor back as cursor.

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

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does disclose that only public replies are returned, that results are paginated one page at a time, and that responses share the /substack/note shape. It does not mention ordering, page size, or behavior on invalid cursors, leaving some gaps but covering core calling behavior.

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 and wastes no words. It front-loads the main purpose, then adds the two most important operational details: one-page behavior and the cursor-based pagination loop.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple paginated read tool with only one required parameter, the description is complete enough: it names the input, the output shape, the public scope, and how to paginate. It would benefit from stating ordering or page size, but nothing critical is missing for an agent to make a correct first call.

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 note_id and cursor. The description reinforces the cursor contract by saying to pass the previous response's next_cursor back, but it does not add meaningfully beyond what the schema already states.

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 uses a specific verb and resource: "List replies to a Substack Note." It also clearly distinguishes this from sibling tools like substack_note_restacks by naming the exact resource being returned (replies), with no ambiguity about what an agent will get.

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 description implies when to use it—when you need replies to a Note—and explains pagination well. However, it does not explicitly address when not to use it or name alternatives such as substack_note_restacks, substack_note, or substack_notes for related but different purposes.

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