RBX Invest Roblox Limiteds market data

Recent UGC Limited releases

get_new_limiteds

UGC Limiteds released recently, with demand level, stock left and the predicted profit numbers RBX Invest scores them with.

Input Schema

TableJSON 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

C2.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden; it partially discharges this by disclosing the returned fields, which is valuable given there is no output schema. However, it never states pagination behavior (page/limit exist), sorting semantics, read-only nature, or any auth/rate-limit context.

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?

A single front-loaded sentence with no filler; the resource and the payload are stated immediately. It is slightly run-on and never states an action verb, but nothing is wasted.

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 listing tool with no annotations and no output schema, the description should cover paging, sort options, and filter semantics. It names only the returned fields and omits everything needed to drive the parameters correctly.

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 56%, with four of nine parameters (sort, limit, availability, max_age_days) carrying no schema description at all. The description adds nothing about any parameter, so the undocumented filters and the sort enum values are left unexplained in both places.

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 names a specific resource (UGC Limiteds released recently) and enumerates the fields returned (demand level, stock left, predicted profit), so an agent knows what it gets. It stops short of differentiating from nearby siblings like get_items, search_items, or find_deals, and uses no explicit verb.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives, even though search_items, get_items, and find_deals overlap in domain. Only an implicit read of 'recent releases' hints at the use case.

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?