Crawlora MCP

hltb_popular

Read-only

List HowLongToBeat's homepage popular-games discovery feed: the same six rows the site renders in its own popular-games module, in the upstream order, each with game id, name, aliases, type, platform list, release year, the profile_popular counter that orders the feed, aggregate completion and review counters, and the four play-style time headline values in seconds with sample counts. Takes no parameters and returns the current page state, so rows and order change over time. Use a row's id with hltb_game for the full record (including per-style average/median/low/high); this feed carries headline values only and no images, review text, lists, accounts or other user data. It shares hltb_game's qualified 2026-11-11 transport, so a blocked or drifted page is an upstream 503, never an empty feed.

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": "hltb_popular"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

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.

AddedNov 11, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds genuinely non-obvious behavior: the response is a live snapshot whose rows and order shift, and a blocked or drifted upstream page surfaces as a 503 rather than a silently empty feed. That last detail is exactly the kind of failure-mode disclosure an agent cannot get from annotations. It stops short of describing pagination or row-count variability beyond 'six rows,' but the operational profile is well covered.

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 action, then layering scope, field inventory, routing to hltb_game, exclusions, and error behavior — every sentence carries information. The field enumeration is long and partially redundant with the output schema, which keeps it from a 5, but nothing is padding.

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 needn't be spelled out, yet the description still names the headline fields and clarifies what is absent (images, review text, lists, accounts, user data). Combined with the volatility note and the 503-vs-empty-feed distinction, an agent has everything needed to call it and interpret results 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?

Zero parameters, so the baseline is 4, and the description correctly states 'Takes no parameters,' confirming the empty schema. No additional parameter meaning is needed or possible here.

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?

Opens with a specific verb and resource: 'List HowLongToBeat's homepage popular-games discovery feed,' then pins scope further ('the same six rows the site renders,' 'in the upstream order'). The final sentence explicitly distinguishes it from sibling hltb_game ('this feed carries headline values only'), so an agent can separate the two without inspecting either 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?

States the selection rule and the alternative outright: use this feed for the headline discovery rows, and 'use a row's id with hltb_game for the full record (including per-style average/median/low/high).' It also flags the constraint that makes the choice consequential — no parameters, snapshot of current page state, values change over time.

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.