Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

substack_leaderboard

Read-only

One page of a Substack category's bestseller leaderboard, pairing each ranked publication with its author. A different surface from substack_category: it exposes the trending ranking (the site's "Rising" tab), validates its ranking values instead of silently defaulting, accepts the extra cross-category id "bestseller", and returns the author alongside the publication. type must be trending, paid, or all. Use a category_id from substack_categories whose in_leaderboard is true.

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": {
      "category_id": "<category_id>"
    },
    "name": "substack_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page. Upstream accepts 0-25 inclusive; 25 rows per page.
typeNoRanking to read: trending, paid, or all. Defaults to trending.
category_idYesRequired category id from /substack/categories whose in_leaderboard is true. Numeric, or the string ids podcast or bestseller.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-schema behavior: it validates ranking values rather than silently defaulting, and it returns the author alongside the publication. It does not mention pagination limits in prose (though the schema does), so not a full 5.

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?

Front-loaded with the core purpose, then differentiation, then constraints. Three dense sentences with little waste, though the list of distinctions is somewhat compressed and could be split for readability.

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 present, return values need not be explained, and the description still notes the author-plus-publication pairing. Combined with schema coverage, prerequisite guidance, and sibling differentiation, an agent has everything needed to call it correctly.

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 adds real meaning: the valid values for 'type' and the origin constraint on 'category_id'. It doesn't re-explain the page parameter beyond what the schema says, keeping it just above baseline.

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 states a specific verb and resource — 'one page of a Substack category's bestseller leaderboard' — and explicitly contrasts itself with the sibling substack_category ('a different surface from substack_category'). An agent can distinguish the two without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit prerequisite ('Use a category_id from substack_categories whose in_leaderboard is true') and names the alternative surface it is not, which is precisely the routing guidance needed. The allowed 'type' values are also restated as a constraint.

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