Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

roblox_rankings

Fetch a Roblox game ranking shelf—top trending, up-and-coming, top playing now, fun with friends, or top revisited—with names, creators, genres, player counts, votes, maturity, age, and URLs.

Instructions

List Roblox game rankings. Returns one Roblox game ranking shelf, chosen by sort_id: top-trending (default), up-and-coming, top-playing-now, fun-with-friends or top-revisited. Each experience has its name, creator, genre, player count, up and down votes, maturity label, minimum age and URL. Shelves are global, not personalised.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sort_idNoRanking shelf: top-trending, up-and-coming, top-playing-now, fun-with-friends, top-revisited

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort_id / enum
      Added value: +[
+  "top-trending",
+  "up-and-coming",
+  "top-playing-now",
+  "fun-with-friends",
+  "top-revisited"
+]
  2. Addedv1.16.2

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose that exactly one shelf is returned and enumerates the fields delivered per experience (name, creator, genre, player count, votes, maturity, age, URL). It omits auth/permission or rate-limit context, so not quite complete.

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 tight sentences: purpose and return unit first, the sort_id selector with default second, and the field/scope context last. Every sentence carries information that helps an agent call and interpret the tool.

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?

There is no output schema, so the description correctly compensates by describing the return payload and the global (non-personalised) caveat. For a zero-required-param enum listing tool, nothing needed to call it 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 enum is already documented, but the description adds the non-obvious default value ('top-trending'), which the schema does not state. That is a genuine increment over the structured field, though it adds no syntactic detail beyond the enum.

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 ('List') and resource ('Roblox game rankings') and immediately clarifies the return unit ('one Roblox game ranking shelf'). This cleanly distinguishes it from siblings like roblox_search, roblox_game, and roblox_badges 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?

Explains how the result is selected via sort_id, names the default ('top-trending'), and adds useful scoping context ('Shelves are global, not personalised'). It does not explicitly name alternative tools or when-not-to-use conditions, so it falls short of a 5.

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

Deploy Server

Other Tools