Crawlora MCP

substack_notes

Read-only

Browse one page of the public Substack Notes feed for a tab. tab and type come as a pair from substack_notes_tabs. Cursor-paginated via next_cursor. Post-only rows are omitted; every returned row is a Note.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "substack_notes"
  }
}

Input Schema

Name	Required	Description
`tab`	No	Feed tab id from /substack/notes/tabs. Defaults to for-you.
`type`	No	Tab type from /substack/notes/tabs: base, secondary, or category. Defaults to base.
`cursor`	No	Opaque cursor from a previous response's next_cursor.

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.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds substantive behavior beyond that: 'Cursor-paginated via next_cursor' and the filtering rule 'Post-only rows are omitted; every returned row is a Note,' which tells the agent what it will and won't receive.

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 short sentences, front-loaded with purpose, then the prerequisite, then the pagination and filtering behavior. Every sentence carries information an agent needs, with zero 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 no explanation; the description covers the remaining unknowns (pagination mechanism, row filtering, parameter provenance) and annotations cover the safety profile. Nothing needed to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description contributes the pairing constraint between tab and type that no individual schema field states -- a real cross-parameter invariant. It doesn't explain cursor expiry or page-size behavior, keeping it below 5.

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 specific verb and resource ('Browse one page of the public Substack Notes feed for a tab'), scoping it to a single paginated page. This distinguishes it from sibling feeds like substack_notes_tabs (the source of the tab) and substack_note (single-note retrieval).

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?

Explicitly tells the agent where tab and type come from (substack_notes_tabs) and that they must be used as a pair, which is real routing guidance. It stops short of naming when NOT to use this tool (e.g., versus substack_note or substack_explore), so it does not reach a 5.

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?