Skip to main content
Glama

insert_asset

Inserts a Roblox marketplace asset by ID into the edit copy and returns its path as one undo step; ownership required for third-party models.

Instructions

Insert a marketplace asset into the edit copy by id and return its path. Recorded as one Studio undo step. Roblox only lets Studio load assets the signed-in user owns, or Roblox-made ones, so most third-party free models fail until the user adds them to their inventory in the Toolbox. Run scan_backdoors after inserting a free model. For a file on this computer use import_file; to generate a new model with AI use generate_asset.

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": "insert_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.
assetIdYesRoblox asset id, e.g. from search_assets.
parentPathNoWhere to put the inserted asset. Dot path from the DataModel root, e.g. "Workspace.Map.Door" or "StarterGui.HUD.Frame". A leading "game." is optional; a duplicate sibling name takes the suffix Tufan prints, e.g. "Part (2)". Omit to use Workspace.

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"
    • addedInput schema / properties / parentPath / description
      Added value: +"Where to put the inserted asset. Dot path from the DataModel root, e.g. \"Workspace.Map.Door\" or \"StarterGui.HUD.Frame\". A leading \"game.\" is optional; a duplicate sibling name takes the suffix Tufan prints, e.g. \"Part (2)\". Omit to use Workspace."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing undo semantics ('Recorded as one Studio undo step'), an authentication/ownership gate that causes most third-party free models to fail, and a post-insert safety recommendation. Annotations already cover the read/write/destructive profile, so this added context is a genuine bonus rather than a required disclosure.

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?

Four dense sentences, front-loaded with the action and its return value, then constraints, then alternatives. Every sentence carries information, though the ownership caveat and the alternatives sentence could be tightened slightly.

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?

With no output schema, the description correctly states the return ('its path'), and it covers mutation side effects, a permission gate, and a recommended follow-up. Nothing essential is missing for correct invocation, though it does not describe failure behavior when ownership 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%, so assetId and parentPath semantics (including the duplicate-sibling suffix behavior) are already fully documented in the schema. The description only reinforces that lookup is 'by id'; it adds no format or constraint detail beyond the structured fields, so 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 ('Insert a marketplace asset into the edit copy by id') plus the return value ('return its path'), which is enough to distinguish it from import_file and generate_asset without opening any 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?

Explicitly routes the agent: 'For a file on this computer use import_file; to generate a new model with AI use generate_asset.' It also states a precondition (ownership/Roblox-made) that determines whether the call can succeed and a follow-up step ('Run scan_backdoors after inserting a free model').

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