RBX Invest Roblox Limiteds market data

Recent UGC Limited releases

get_new_limiteds

UGC Limiteds released recently, with stock left, the predicted profit numbers RBX Invest scores them with, and each item’s demand_level: the Est. Demand the feed card shows, a release-time estimate of how fast the creator’s copies sell out, ranked in quarters against the last 90 days of paid releases (excellent = fastest). Sell-out speed only, not a buy signal or a guarantee; the reply carries the meaning in demand_level_meaning.

Input Schema

Name	Required	Description	Default
`page`	No	Page of the results, for reading past the first.
`sort`	No		newest
`limit`	No
`query`	No	Part of an item name, to search within recent releases.
`hide_free`	No	Drop items the creator released at 0 R$.
`availability`	No		all
`max_age_days`	No
`resellable_only`	No	Only items whose resale window has opened.
`all_experiences_only`	No	Only items sold in any experience — the ones a buyer can list in their own game and keep the 40% affiliate commission on.

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 results, for reading past the first.",
+  "maximum": 20,
+  "minimum": 1,
+  "type": "integer"
+}

First observedSep 6, 2026

TDQS

B3/5.0

Behavior3/5

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

No annotations are supplied, so the description must carry behavioral context; it usefully explains that demand_level is a release-time sell-out estimate ranked against the last 90 days and is not a buy signal or guarantee. It still does not disclose permissions, pagination behavior, or broader response semantics for the nine-parameter read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening is front-loaded with the core scope, but the single long sentence packs in multiple nested explanations and repeats demand_level context, making it denser than necessary. It is not bloated with irrelevant text, but structure could be clearer.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter tool with no annotations and no output schema, the description covers only the high-level feed and demand_level meaning. It omits enough parameter and response detail that an agent would need to rely heavily on the schema and still lack completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 56%, and the description does not explain sort, limit, availability, or max_age_days semantics beyond broad phrases like 'recently' and 'stock left'. It therefore leaves several parameters to be inferred from the schema rather than compensating for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the resource (recent UGC Limiteds with remaining stock) and the return content (predicted profit and demand_level), so the core purpose is clear. It does not explicitly contrast itself with sibling tools like search_items or get_items, so it stops short of a 5.

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

Usage Guidelines3/5

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

The recency and stock constraints imply the use case, and the caveat that demand_level is sell-out speed only clarifies interpretation. However, there is no explicit when-to-use or when-not guidance and no named alternative among the many sibling tools.

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?