Skip to main content
Glama

RBX Invest Roblox Limiteds market data

by com.rbxinvest
OverviewDiscussionsAdmin

Search or rank Roblox Limiteds

search_items

Search the Roblox Limited catalog by name, or screen the whole market when no query is given. Returns asset id, RAP, RAP across every copy sold, the lowest resale listing, stock left, the move in RAP over 1/7/14/30 days and lifetime in both percent and Robux, sales counts and sales value per window, and the item score. Rank by any of those with sort, and bound any of them with filters to ask a question with more than one condition in it. Prices are Robux.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoMetric to rank by. Size: rap, totalValue, price (cheapest copy from any seller), creatorPrice (the creator's price for a new copy; only items still on sale from the creator have one), copies, copiesLeft, percentRemaining (stock still unsold, the reading the site shows), percentSold (its complement), score. Movement: growth1d/7d/14d/30d/all (percent) and growthRs1d/7d/14d/30d/all (the same move in Robux); only items that sold inside the window have one, and the "all" pair measures against the creator's original price. Trading: volume1d/7d/14d/30d (sales) and salesTotal1d/7d/14d/30d (Robux moved).rap
limitNo
queryNoPart of an item name, e.g. "valkyrie". Omit to rank or screen the catalog.
offsetNoRows to skip, for reading past the first page. The reply reports the total that matched.
filtersNoRanges narrowing the catalog, ANDed together. Each is in the unit its metric is shown in: Robux for rap/totalValue/price/creatorPrice/salesTotal*/growthRs*, percent for growth*/percentRemaining/percentSold, a count for copies/copiesLeft/volume*. An item with no value for a bounded metric is excluded.
directionNodesc
item_typeNoregular_limited is a classic Limited, ugc_limited a UGC one.all
asset_typeNoOnly this kind of item, e.g. Hat, HairAccessory, FaceAccessory, BackAccessory, Face, Gear. Omit for every kind.
availabilityNoavailable = copies still in stock from the creator.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / asset_type / enum
      Previous value: -[
-  "AvatarBackground",
-  "BackAccessory",
-  "DressSkirtAccessory",
-  "DynamicHead",
-  "EmoteAnimation",
-  "EyebrowAccessory",
-  "EyelashAccessory",
-  "Face",
-  "FaceAccessory",
-  "FaceMakeup",
-  "FrontAccessory",
-  "Gear",
-  "HairAccessory",
-  "Hat",
-  "JacketAccessory",
-  "LeftShoeAccessory",
-  "LipMakeup",
-  "NeckAccessory",
-  "PantsAccessory",
-  "ShirtAccessory",
-  "ShortsAccessory",
-  "ShoulderAccessory",
-  "SweaterAccessory",
-  "TShirtAccessory",
-  "WaistAccessory"
-]New value: +[
+  "AvatarBackground",
+  "BackAccessory",
+  "DressSkirtAccessory",
+  "DynamicHead",
+  "EmoteAnimation",
+  "EyebrowAccessory",
+  "EyelashAccessory",
+  "EyeMakeup",
+  "Face",
+  "FaceAccessory",
+  "FaceMakeup",
+  "FrontAccessory",
+  "Gear",
+  "HairAccessory",
+  "Hat",
+  "JacketAccessory",
+  "LeftShoeAccessory",
+  "LipMakeup",
+  "NeckAccessory",
+  "PantsAccessory",
+  "ShirtAccessory",
+  "ShortsAccessory",
+  "ShoulderAccessory",
+  "SweaterAccessory",
+  "TShirtAccessory",
+  "WaistAccessory"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / asset_type / enum
      Previous value: -[
-  "AvatarBackground",
-  "BackAccessory",
-  "DressSkirtAccessory",
-  "DynamicHead",
-  "EmoteAnimation",
-  "EyebrowAccessory",
-  "EyelashAccessory",
-  "Face",
-  "FaceAccessory",
-  "FrontAccessory",
-  "Gear",
-  "HairAccessory",
-  "Hat",
-  "JacketAccessory",
-  "LeftShoeAccessory",
-  "NeckAccessory",
-  "PantsAccessory",
-  "ShirtAccessory",
-  "ShortsAccessory",
-  "ShoulderAccessory",
-  "SweaterAccessory",
-  "TShirtAccessory",
-  "WaistAccessory"
-]New value: +[
+  "AvatarBackground",
+  "BackAccessory",
+  "DressSkirtAccessory",
+  "DynamicHead",
+  "EmoteAnimation",
+  "EyebrowAccessory",
+  "EyelashAccessory",
+  "Face",
+  "FaceAccessory",
+  "FaceMakeup",
+  "FrontAccessory",
+  "Gear",
+  "HairAccessory",
+  "Hat",
+  "JacketAccessory",
+  "LeftShoeAccessory",
+  "LipMakeup",
+  "NeckAccessory",
+  "PantsAccessory",
+  "ShirtAccessory",
+  "ShortsAccessory",
+  "ShoulderAccessory",
+  "SweaterAccessory",
+  "TShirtAccessory",
+  "WaistAccessory"
+]
  3. Changed1 schema field changed
    • addedInput schema / properties / asset_type
      Added value: +{
+  "description": "Only this kind of item, e.g. Hat, HairAccessory, FaceAccessory, BackAccessory, Face, Gear. Omit for every kind.",
+  "enum": [
+    "AvatarBackground",
+    "BackAccessory",
+    "DressSkirtAccessory",
+    "DynamicHead",
+    "EmoteAnimation",
+    "EyebrowAccessory",
+    "EyelashAccessory",
+    "Face",
+    "FaceAccessory",
+    "FrontAccessory",
+    "Gear",
+    "HairAccessory",
+    "Hat",
+    "JacketAccessory",
+    "LeftShoeAccessory",
+    "NeckAccessory",
+    "PantsAccessory",
+    "ShirtAccessory",
+    "ShortsAccessory",
+    "ShoulderAccessory",
+    "SweaterAccessory",
+    "TShirtAccessory",
+    "WaistAccessory"
+  ],
+  "type": "string"
+}
  4. Changed4 schema fields changed
    • changedInput schema / properties / filters / description
      Previous value: -"Ranges narrowing the catalog, ANDed together. Each is in the unit its metric is shown in: Robux for rap/totalValue/price/salesTotal*/growthRs*, percent for growth*/percentRemaining/percentSold, a count for copies/copiesLeft/volume*. An item with no value for a bounded metric is excluded."New value: +"Ranges narrowing the catalog, ANDed together. Each is in the unit its metric is shown in: Robux for rap/totalValue/price/creatorPrice/salesTotal*/growthRs*, percent for growth*/percentRemaining/percentSold, a count for copies/copiesLeft/volume*. An item with no value for a bounded metric is excluded."
    • changedInput schema / properties / filters / items / properties / metric / enum
      Previous value: -[
-  "rap",
-  "totalValue",
-  "price",
-  "growth1d",
-  "growth7d",
-  "growth14d",
-  "growth30d",
-  "growthall",
-  "growthRs1d",
-  "growthRs7d",
-  "growthRs14d",
-  "growthRs30d",
-  "growthRsall",
-  "score",
-  "copies",
-  "copiesLeft",
-  "percentSold",
-  "percentRemaining",
-  "volume1d",
-  "volume7d",
-  "volume14d",
-  "volume30d",
-  "demandGrowth1d",
-  "demandGrowth7d",
-  "demandGrowth14d",
-  "demandGrowth30d",
-  "salesTotal1d",
-  "salesTotal7d",
-  "salesTotal14d",
-  "salesTotal30d"
-]New value: +[
+  "rap",
+  "totalValue",
+  "price",
+  "creatorPrice",
+  "growth1d",
+  "growth7d",
+  "growth14d",
+  "growth30d",
+  "growthall",
+  "growthRs1d",
+  "growthRs7d",
+  "growthRs14d",
+  "growthRs30d",
+  "growthRsall",
+  "score",
+  "copies",
+  "copiesLeft",
+  "percentSold",
+  "percentRemaining",
+  "volume1d",
+  "volume7d",
+  "volume14d",
+  "volume30d",
+  "demandGrowth1d",
+  "demandGrowth7d",
+  "demandGrowth14d",
+  "demandGrowth30d",
+  "salesTotal1d",
+  "salesTotal7d",
+  "salesTotal14d",
+  "salesTotal30d"
+]
    • changedInput schema / properties / sort / description
      Previous value: -"Metric to rank by. Size: rap, totalValue, price, copies, copiesLeft, percentRemaining (stock still unsold, the reading the site shows), percentSold (its complement), score. Movement: growth1d/7d/14d/30d/all (percent) and growthRs1d/7d/14d/30d/all (the same move in Robux); only items that sold inside the window have one, and the \"all\" pair measures against the creator's original price. Trading: volume1d/7d/14d/30d (sales) and salesTotal1d/7d/14d/30d (Robux moved)."New value: +"Metric to rank by. Size: rap, totalValue, price (cheapest copy from any seller), creatorPrice (the creator's price for a new copy; only items still on sale from the creator have one), copies, copiesLeft, percentRemaining (stock still unsold, the reading the site shows), percentSold (its complement), score. Movement: growth1d/7d/14d/30d/all (percent) and growthRs1d/7d/14d/30d/all (the same move in Robux); only items that sold inside the window have one, and the \"all\" pair measures against the creator's original price. Trading: volume1d/7d/14d/30d (sales) and salesTotal1d/7d/14d/30d (Robux moved)."
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "rap",
-  "totalValue",
-  "price",
-  "growth1d",
-  "growth7d",
-  "growth14d",
-  "growth30d",
-  "growthall",
-  "growthRs1d",
-  "growthRs7d",
-  "growthRs14d",
-  "growthRs30d",
-  "growthRsall",
-  "score",
-  "copies",
-  "copiesLeft",
-  "percentSold",
-  "percentRemaining",
-  "volume1d",
-  "volume7d",
-  "volume14d",
-  "volume30d",
-  "demandGrowth1d",
-  "demandGrowth7d",
-  "demandGrowth14d",
-  "demandGrowth30d",
-  "salesTotal1d",
-  "salesTotal7d",
-  "salesTotal14d",
-  "salesTotal30d"
-]New value: +[
+  "rap",
+  "totalValue",
+  "price",
+  "creatorPrice",
+  "growth1d",
+  "growth7d",
+  "growth14d",
+  "growth30d",
+  "growthall",
+  "growthRs1d",
+  "growthRs7d",
+  "growthRs14d",
+  "growthRs30d",
+  "growthRsall",
+  "score",
+  "copies",
+  "copiesLeft",
+  "percentSold",
+  "percentRemaining",
+  "volume1d",
+  "volume7d",
+  "volume14d",
+  "volume30d",
+  "demandGrowth1d",
+  "demandGrowth7d",
+  "demandGrowth14d",
+  "demandGrowth30d",
+  "salesTotal1d",
+  "salesTotal7d",
+  "salesTotal14d",
+  "salesTotal30d"
+]
  5. Changed3 schema fields changed
    • changedInput schema / properties / filters / items / properties / metric / enum
      Previous value: -[
-  "rap",
-  "totalValue",
-  "price",
-  "growth1d",
-  "growth7d",
-  "growth30d",
-  "growthall",
-  "growthRs1d",
-  "growthRs7d",
-  "growthRs30d",
-  "growthRsall",
-  "score",
-  "copies",
-  "copiesLeft",
-  "percentSold",
-  "percentRemaining",
-  "volume1d",
-  "volume7d",
-  "volume30d",
-  "demandGrowth1d",
-  "demandGrowth7d",
-  "demandGrowth30d",
-  "salesTotal1d",
-  "salesTotal7d",
-  "salesTotal30d"
-]New value: +[
+  "rap",
+  "totalValue",
+  "price",
+  "growth1d",
+  "growth7d",
+  "growth14d",
+  "growth30d",
+  "growthall",
+  "growthRs1d",
+  "growthRs7d",
+  "growthRs14d",
+  "growthRs30d",
+  "growthRsall",
+  "score",
+  "copies",
+  "copiesLeft",
+  "percentSold",
+  "percentRemaining",
+  "volume1d",
+  "volume7d",
+  "volume14d",
+  "volume30d",
+  "demandGrowth1d",
+  "demandGrowth7d",
+  "demandGrowth14d",
+  "demandGrowth30d",
+  "salesTotal1d",
+  "salesTotal7d",
+  "salesTotal14d",
+  "salesTotal30d"
+]
    • changedInput schema / properties / sort / description
      Previous value: -"Metric to rank by. Size: rap, totalValue, price, copies, copiesLeft, percentRemaining (stock still unsold, the reading the site shows), percentSold (its complement), score. Movement: growth1d/7d/30d/all (percent) and growthRs1d/7d/30d/all (the same move in Robux); only items that sold inside the window have one, and the \"all\" pair measures against the creator's original price. Trading: volume1d/7d/30d (sales) and salesTotal1d/7d/30d (Robux moved)."New value: +"Metric to rank by. Size: rap, totalValue, price, copies, copiesLeft, percentRemaining (stock still unsold, the reading the site shows), percentSold (its complement), score. Movement: growth1d/7d/14d/30d/all (percent) and growthRs1d/7d/14d/30d/all (the same move in Robux); only items that sold inside the window have one, and the \"all\" pair measures against the creator's original price. Trading: volume1d/7d/14d/30d (sales) and salesTotal1d/7d/14d/30d (Robux moved)."
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "rap",
-  "totalValue",
-  "price",
-  "growth1d",
-  "growth7d",
-  "growth30d",
-  "growthall",
-  "growthRs1d",
-  "growthRs7d",
-  "growthRs30d",
-  "growthRsall",
-  "score",
-  "copies",
-  "copiesLeft",
-  "percentSold",
-  "percentRemaining",
-  "volume1d",
-  "volume7d",
-  "volume30d",
-  "demandGrowth1d",
-  "demandGrowth7d",
-  "demandGrowth30d",
-  "salesTotal1d",
-  "salesTotal7d",
-  "salesTotal30d"
-]New value: +[
+  "rap",
+  "totalValue",
+  "price",
+  "growth1d",
+  "growth7d",
+  "growth14d",
+  "growth30d",
+  "growthall",
+  "growthRs1d",
+  "growthRs7d",
+  "growthRs14d",
+  "growthRs30d",
+  "growthRsall",
+  "score",
+  "copies",
+  "copiesLeft",
+  "percentSold",
+  "percentRemaining",
+  "volume1d",
+  "volume7d",
+  "volume14d",
+  "volume30d",
+  "demandGrowth1d",
+  "demandGrowth7d",
+  "demandGrowth14d",
+  "demandGrowth30d",
+  "salesTotal1d",
+  "salesTotal7d",
+  "salesTotal14d",
+  "salesTotal30d"
+]
  6. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It explains the no-query behavior, the computed return fields, the units, and the ranking/filtering capabilities. It does not mention pagination behavior or response shape, but those are covered in the schema and the behavior described is otherwise transparent.

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 dense sentences with no filler: the first states the core capability, the second enumerates return fields, and the third explains ranking, filtering, and units. The most important scoping behavior is front-loaded.

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?

Given 9 parameters, 5 enums, and no output schema, the description is quite complete: it explains return fields, the no-query screen behavior, ranking, filtering, and units. It could additionally describe the exact output shape or maximum result size, but the rich schema covers most of those details.

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 description coverage is 78%, so the schema already does much of the work. The description adds useful semantic context by mapping return concepts to sort/filter metrics and stating that prices are in Robux. It could name parameter specifics more directly, but it meaningfully complements 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?

The description names a specific verb and resource: searching or ranking the Roblox Limited catalog, and it adds the key scope distinction that omitting the query screens the whole market. This clearly separates it from item-detail and new-limiteds siblings by emphasizing market-wide ranking and filtering.

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?

The description gives clear usage contexts: search by name when you have a name, screen the whole market when you don't, and use sort/filters to ask multi-condition questions. It does not explicitly name sibling tools or give when-not-to-use guidance, so it stops 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.

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