RBX Invest Roblox Limiteds market data

Rank Roblox UGC creators

rank_creators

Creators ranked across the whole Roblox Limited market — who is biggest, and whose releases most often end up profitable. get_creator answers about one creator you can already name; this finds them. Ranking by profitability shows only creators with enough settled releases to rate, and by growth only those with 3 or more items, because an average over one release is noise.

Input Schema

Name	Required	Description	Default
`sort`	No	chance = how often their releases end up profitable, score = RBX Invest's creator rating, totalValue = RAP across everything they have made, copies = copies of their items in circulation, uniqueItems = how many Limiteds they have released, growth = average lifetime appreciation against the price they first sold at (the lifetime measure, not the windowed move the item sorts call growth).	totalValue
`limit`	No
`query`	No	Part of a creator name, to rank within matching creators.
`offset`	No	Rows to skip, for reading past the first page (at most 10,000).
`direction`	No		desc

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

changedInput schema / properties / sort / description

Previous value: -"chance = how often their releases end up profitable, score = RBX Invest's creator rating, totalValue = RAP across everything they have made, copies = copies of their items in circulation, uniqueItems = how many Limiteds they have released, growth = average lifetime appreciation against the price they first sold at (the old measure, not the windowed move the item sorts call growth)."New value: +"chance = how often their releases end up profitable, score = RBX Invest's creator rating, totalValue = RAP across everything they have made, copies = copies of their items in circulation, uniqueItems = how many Limiteds they have released, growth = average lifetime appreciation against the price they first sold at (the lifetime measure, not the windowed move the item sorts call growth)."

Changed3 schema fields changedOct 5, 2026

changedInput schema / properties / limit / maximum
```
Previous value: -25New value: +100
```

changedInput schema / properties / offset / description

Previous value: -"Rows to skip, for reading past the first page (at most 500)."New value: +"Rows to skip, for reading past the first page (at most 10,000)."

changedInput schema / properties / offset / maximum
```
Previous value: -500New value: +10000
```

Changed2 schema fields changedOct 5, 2026

changedInput schema / properties / offset / description

Previous value: -"Rows to skip, for reading past the first page."New value: +"Rows to skip, for reading past the first page (at most 500)."

addedInput schema / properties / offset / maximum
```
Added value: +500
```

First observedSep 6, 2026

TDQS

A4.6/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 does disclose a non-obvious behavioral trait: the ranked population changes with the sort (only creators with settled releases for 'chance', 3+ items for 'growth'). It does not cover pagination limits or whether ranking is deterministic, so it is strong but not 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 sentences, front-loaded with the core purpose, then the sibling routing, then the sort caveats. No filler; the final clause ('an average over one release is noise') explains the rationale rather than padding.

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?

All five parameters are optional and the description plus schema cover how to call it correctly. With no output schema, however, it never says what a ranked row contains (name, rating, metrics), leaving the agent to infer the response shape.

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?

Adds real meaning beyond the 60%-covered schema, notably clarifying that 'growth' here is the lifetime appreciation measure, not the windowed move used by item sorts — a cross-tool disambiguation the enum text alone does not make. 'limit', 'direction' and 'query' are left to the schema, which mostly covers them.

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 and resource ('Creators ranked across the whole Roblox Limited market') plus the two axes of interest (size and profitability). It explicitly distinguishes itself from the sibling get_creator, so an agent can route without opening 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?

Names the alternative tool and the exact condition that selects it: 'get_creator answers about one creator you can already name; this finds them.' It also warns which creators drop out of the result set under the 'chance' and 'growth' sorts, which is practical when-to-use guidance.

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

All RBX Invest Roblox Limiteds market data 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?