Inspect and edit glTF assets with Scene Drill

Use the Scene Drill website through browser controls to load a supplied model, inspect and edit supported properties, then download and reopen the result. This guide describes that browser workflow.

What your agent needs

Your agent needs browser control, a browser with WebGL 2, and tools that can upload the supplied files and save downloads. Chat-only agents and tools that only read web pages cannot execute this workflow. If file handling or browser control is unavailable, report that limitation.

The application performs these actions through its browser interface and in-app Console. This guide does not provide a hosted HTTP API or MCP endpoint.

Supported programmable edits

Inspect node hierarchy, authored local transforms, materials and shared material users.
Rename existing nodes and set supported authored local translation, rotation or scale.
Change ordinary material metallic, roughness and linear RGB base color factors.
Group supported edits into a finite atomic transaction.

Use the Console's API help for exact arguments, units, examples and limits. Animated properties, joints, matrix transforms, whole-asset Placement and some materials have restrictions. Read returned refusal reasons and stop when a required change is unsupported. These programmable operations do not cover geometry creation, topology or UV/rig authoring, texture replacement, alpha changes or general animation authoring.

Inspect, edit, export and verify

Load the supplied model. Open Scene Drill and use its file controls to load a GLB or a complete glTF package, including required buffers and textures. Review the Replace or Add choice when the loading dialog appears. Confirm the intended model has loaded before editing.
Open Operations → Console. Operations is in the header, or the menu on a narrow screen. Choose Source if the editor is hidden. Run this inspection example:
```
const page = await scene.nodes({ limit: 25 })
return page
```
Read the returned output in Results. Use the API help and Query and edit examples for scene.node, scene.materials, scene.material and app.capabilities.
Resolve exact targets. Names identify candidates; confirm the intended identity, hierarchy and authored values before a write. Follow every non-null pagination cursor with the same limit until the cursor is null. Also check complete and incompleteReason; report truncation or incomplete results. A changed document invalidates prior cursors. Inspect every shared material user before changing its factors. Insert selected reference can insert the Explorer selection's current reference into the source.
Make a deliberate supported edit. Use the generated edit examples and API declarations in the Console. Top-level await is supported; return displays a result. Click Run explicitly and check each operation's acknowledgment. Ordinary writes commit separately; use scene.transaction for one atomic group. Stop or a later script error does not undo earlier commits.
Review the outcome. Inspect History for the concrete before/after receipt and use supported Undo/Redo when appropriate. Source-editor undo changes the script draft, not the model. Confirm the requested authored values and relevant unaffected properties.
Export actual files. Use Export and choose GLB or a packaged glTF ZIP, with the required compression and image options. Save the actual download and retain validation warnings. A successful Console result or a screenshot alone does not establish a delivered model.
Reopen and verify the download. Open another Scene Drill tab and load the downloaded GLB or the complete extracted glTF package. Check the edited values, relevant unaffected properties and expected appearance. Verify each format you deliver. Give the human the actual output file, a concise change summary and any warnings or checks you could not complete.

History and patches

History records supported edits and linked Undo/Redo. Retained local history does not restore model bytes after a reload; export the asset separately.

Download patch saves complete supported effective changes from the current baseline. If History reports incomplete coverage, Start new baseline captures a baseline GLB to keep before making further edits.

In Operations → Replay, Import patch opens a data-only patch for review. Importing does not apply it. Revised assets use Bindings to review correspondence, then Decisions to compare Expected, Current and Requested values. Choose Keep current, Use patch or Adjust; an adjustment needs Review adjustment. Recheck after document changes and review shared material users before Apply revised patch.