RBX Invest Roblox Limiteds market data

Limiteds listed below RAP

find_deals

Roblox Limiteds whose lowest resale listing is currently below their RAP, with the discount and the absolute saving. This is the live resale market, refreshed continuously. Use it for what is underpriced right now.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Page of the feed, for reading past the first. The reply says how many are listed in total.
`sort`	No	deal = biggest discount, savings = biggest absolute saving, recent = newest; rap and price rank by those.	deal
`type`	No	ugc_limited or regular_limited (classic).	ugc_limited
`limit`	No
`min_rap`	No	Ignore items whose RAP is below this.
`max_price`	No	Highest resale price to consider, in Robux.
`min_price`	No	Lowest resale price to consider, in Robux.
`min_discount_pct`	No	Only items at least this far below RAP.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 5, 2026
- changedInput schema / properties / limit / maximum
```
Previous value: -25New value: +200
```
- changedInput schema / properties / page / maximum
```
Previous value: -20New value: +100
```

Changed1 schema field changedOct 5, 2026

addedInput schema / properties / page

Added value: +{
+  "default": 1,
+  "description": "Page of the feed, for reading past the first. The reply says how many are listed in total.",
+  "maximum": 20,
+  "minimum": 1,
+  "type": "integer"
+}

First observedSep 6, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations, so the description carries the full disclosure burden. It usefully adds that this is the live resale market refreshed continuously, which matters because RAP-relative deals can go stale, but it says nothing about read-only nature, auth, rate limits, or the reply's shape beyond the discount fields.

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?

Three short sentences, front-loaded with the definition, then freshness, then the use case. The final sentence slightly restates the first ("underpriced" vs "below RAP"), a minor redundancy in an otherwise tight description.

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?

For an 8-parameter, no-required-arg tool with no annotations and no output schema, the description adequately frames the result set and the live nature of the data, and it hints at the returned discount/savings fields. It leaves filter semantics entirely to the schema, which is acceptable at 88% coverage.

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 88%, so the schema already documents page, sort, type, min_rap, price bounds and min_discount_pct. The description's mention of "discount and the absolute saving" loosely maps to the deal/savings sort semantics but adds no syntax or format detail beyond the schema.

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 precise criterion (Limiteds whose lowest resale listing is below RAP) plus what is returned (discount and absolute saving). This is inherently distinct from siblings like get_new_limiteds (novelty) and search_items (query-based), so an agent can route to it without opening the 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?

"Use it for what is underpriced right now" gives a clear when-to-use context tied to the live market. It does not name an alternative or state when not to use it (e.g. vs. get_new_limiteds), so it stops short of full routing 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?