Skip to main content
Glama

get_asset_details

Read-only

Fetch public Roblox marketplace details for an asset ID as JSON, including name, creator, asset type, description, dates, and sale status.

Instructions

Fetch public marketplace details for one asset id as JSON: name, creator, asset type, description, created and updated dates, and whether it is for sale. Read-only; uses Roblox's public economy API. It does not say whether a model contains scripts, so run scan_backdoors after inserting one. To see the asset, use get_asset_thumbnail.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "assetId": "<assetId>"
    },
    "name": "get_asset_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdYesRoblox asset id, e.g. from search_assets or a Creator Store URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / assetId / description
      Added value: +"Roblox asset id, e.g. from search_assets or a Creator Store URL."
    • addedInput schema / properties / assetId / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / assetId / minimum
      Added value: +-9007199254740991
    • changedInput schema / properties / assetId / type
      Previous value: -"number"New value: +"integer"
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint; the description reinforces read-only and specifies the upstream source ('Roblox's public economy API'), implying public, unauthenticated data. Its most valuable addition is disclosing a content blind spot — no script information — with a recommended follow-up call. It does not discuss error behavior or rate limiting, so it stops short of full transparency.

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 return payload, then the behavioral note, then the sibling routing. Every sentence carries distinct information and none restates the name or title.

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

Completeness5/5

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

There is no output schema, yet the description compensates by listing the returned fields, and it covers the two things an agent would otherwise get wrong: expecting script scanning and expecting image rendering. Nothing essential for a correct call is missing.

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?

With a single parameter at 100% schema description coverage, the schema already explains that assetId is a Roblox asset id derivable from search_assets or a Creator Store URL. The description adds only the 'one asset id' singularity, which is the expected baseline rather than added meaning.

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 ('Fetch public marketplace details for one asset id') and then enumerates exactly what comes back: name, creator, asset type, description, dates, and for-sale status. It is trivially distinguishable from get_asset_thumbnail and scan_backdoors, both of which it names.

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?

Explicitly routes the agent: use get_asset_thumbnail 'to see the asset', and run scan_backdoors after inserting a model because this tool cannot report script contents. It also scopes usage to a single asset id, so the agent knows this is not a bulk lookup.

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