Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

substack_explore

Read-only

Fetch Substack Explore's mixed feed of modules such as trending topics, posts, bestsellers, videos, and category leaders. Use substack_search for a query or substack_notes for note-specific content.

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

Input Schema

NameRequiredDescriptionDefault
tabNoExplore tab id from the tabs endpoint with surface=explore. Defaults to explore.
typeNoTab type: base, secondary, or category. Defaults to base.
cursorNoOpaque cursor from a previous response's next_cursor.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data scope are covered. The description adds that the feed is a mix of heterogeneous modules, which is useful context, but it discloses no pagination behavior, refresh cadence, or auth requirements beyond what annotations and the cursor parameter already imply.

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?

Two sentences, no filler. The capability statement is front-loaded and the routing guidance follows immediately. Every clause earns its place.

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?

With an output schema documenting return values, full parameter coverage, and annotations covering the safety profile, the description needs only to establish purpose and routing, which it does. It is nearly complete for a read-only feed tool; only cross-sibling browsing guidance is absent.

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% and all three parameters (tab, type, cursor) are documented in the schema, so the baseline is 3. The description adds no additional meaning about parameter values, defaults, or valid combinations.

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 ('Fetch') and resource ('Substack Explore's mixed feed of modules'), and enumerates the module kinds it returns (trending topics, posts, bestsellers, videos, category leaders). This lets an agent distinguish it from search- and notes-oriented siblings without opening any schema.

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 routes the agent: 'Use substack_search for a query or substack_notes for note-specific content.' That names two alternatives and the conditions selecting them. It does not, however, address when to prefer this over other browsing siblings like substack_leaderboard or substack_categories.

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

All Crawlora MCP toolsInspect
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