Skip to main content
Glama

get_asset_thumbnail

Read-only

Fetch a Roblox asset's thumbnail as a PNG to preview its catalog art before inserting it. Works for any public asset, owned or not.

Instructions

Return an asset's thumbnail as a PNG image, so you can see what it looks like before inserting it. Read-only; uses Roblox's public thumbnail API and works for any public asset, owned or not. For text details use get_asset_details. This shows catalog art only; to see the open place use the official Studio MCP's screen_capture.

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_thumbnail"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoImage size in pixels. Default 420x420.
assetIdYesRoblox asset id, e.g. from search_assets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • addedInput schema / properties / assetId / description
      Added value: +"Roblox asset id, e.g. from search_assets."
    • 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"
    • changedInput schema / properties / size / description
      Previous value: -"default 420x420"New value: +"Image size in pixels. Default 420x420."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds the meaningful constraint that it relies on Roblox's public thumbnail API and is limited to public assets. It omits failure modes such as assets with no thumbnail or moderation-pending art, which would matter for a single-image fetch.

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 short sentences, front-loaded with the action and output format, followed by usage routing. No filler or restated title text.

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 a two-parameter read-only image fetch with no output schema, the description covers purpose, scope, output format, and alternatives. Only the behavior when no thumbnail exists is left unstated.

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 coverage is 100%, with assetId documented (including a pointer to search_assets) and size enumerated with a stated default. The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

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 ("Return an asset's thumbnail as a PNG image") plus the intent ("see what it looks like before inserting it"). It explicitly distinguishes itself from both get_asset_details (text details) and screen_capture (open place), so an agent can pick it without opening another schema.

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?

Gives explicit routing: use get_asset_details for text metadata, screen_capture for the live place, this tool for catalog art. It also states a scope condition -- works for any public asset, owned or not -- which tells the agent when the tool will succeed.

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