Crawlora MCP

substack_notes_tabs

Read-only

List every selectable tab for one Substack surface. The two surfaces expose different tab sets: feed has 34 tabs (main feed, bestsellers, one per category) and explore has 33. Each row's id and type must be passed together to the matching feed tool, which rejects a tab whose type does not match.

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_tabs"
  }
}

Input Schema

Name	Required	Description	Default
`surface`	No	Which surface's tabs to list: feed or explore. Defaults to feed.

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

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety burden is light. The description adds real behavioral context beyond annotations: the tab counts per surface (34 vs 33), the composition of the feed tab set, and a downstream constraint that the feed tool rejects mismatched type. That downstream rejection detail is valuable and non-obvious.

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 sentences, front-loaded with the purpose, then the surface distinction, then the critical id/type pairing constraint. Efficient with no filler, though the tab-count specifics (34/33) are slightly decorative.

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?

An output schema exists, so return-value explanation is not required. For a one-parameter read tool, the description supplies the essential integration constraint (pass id and type together; mismatches are rejected) and the surface distinction. It omits naming the exact sibling feed tool, which is the main residual gap.

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 coverage is 100% and the description adds only that the two surfaces expose different tab sets (34 vs 33), which reinforces the semantic of the 'surface' parameter but does not add syntax or default behavior beyond the schema. Baseline 3 is appropriate when the schema already documents the single parameter.

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?

States a specific verb and resource: 'List every selectable tab for one Substack surface,' which is clear and actionable. It does not reference the sibling feed tool by name (e.g., the feed-consuming tool), so it misses the sibling-differentiation that would earn a 5.

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?

Explains the workflow context: the returned id and type must be passed together to the matching feed tool. This tells the agent when this tool is needed (as a discovery step before fetching a feed). It does not name the specific alternative/sibling tool or state exclusions, keeping it below 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?