Skip to main content
Glama

search_assets

Read-only

Search Roblox Creator Store assets by keyword to get matching asset IDs, names, and creators. Follow up with asset details, thumbnails, or insertion into Studio.

Instructions

Search the Roblox Creator Store (Studio's Toolbox) by keyword and list matching asset ids with name and creator. Read-only; calls Roblox's public web APIs and needs no Studio. Follow up with get_asset_details or get_asset_thumbnail, then insert_asset. Roblox no longer reports whether a model contains scripts, so run scan_backdoors after inserting a free model. To find instances already in the place use search_objects.

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": {
      "keyword": "<keyword>"
    },
    "name": "search_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results, up to 30. Default 15.
keywordYesSearch words, e.g. "medieval house" or "sword".
assetTypeNoMarketplace category to search. Default Model.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • changedInput schema / properties / assetType / description
      Previous value: -"default Model"New value: +"Marketplace category to search. Default Model."
    • addedInput schema / properties / keyword / description
      Added value: +"Search words, e.g. \"medieval house\" or \"sword\"."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum results, up to 30. Default 15."
    • addedInput schema / properties / limit / maximum
      Added value: +30
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
  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, but the description adds real context beyond them: it calls Roblox's public web APIs and needs no Studio session, which explains a remote dependency annotations alone don't convey. The caveat that Roblox no longer reports whether a model contains scripts is a genuinely useful behavioral warning. It stops short of mentioning rate limits or pagination, so it is strong rather than complete.

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?

Purpose and read-only status are front-loaded, followed by the follow-up chain and the disambiguation, with no filler sentences. It is dense with useful content, though the workflow chain plus safety caveat makes it longer than strictly minimal.

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?

Covers purpose, return shape, environment requirements, workflow sequencing, and a safety caveat for a tool with rich annotations and full schema coverage. For a keyword search with no output schema, nothing an agent needs in order to call it correctly 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?

Schema description coverage is 100%, with keyword, limit, and assetType all documented including the enum values, so the schema carries the parameter burden. The description adds no syntax, defaults, or format detail beyond what the schema already states. 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 ('Search the Roblox Creator Store (Studio's Toolbox) by keyword'), names the returned fields (asset ids with name and creator), and explicitly distinguishes itself from search_objects, which finds instances already in the place. An agent can route between the two without opening either 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 an explicit tool chain: search here, then get_asset_details or get_asset_thumbnail, then insert_asset, and run scan_backdoors after inserting a free model. It also names the alternative (search_objects) and the condition that selects it, so both when-to-use and when-not-to-use are covered.

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