Skip to main content
Glama

mass_edit

DestructiveIdempotent

Batch many Roblox property changes across instances into one undo step; report each failed edit by index and reason while applying valid changes.

Instructions

Apply many property changes, across any number of instances, in one call recorded as one Studio undo step. Each edit is tried on its own: failures (unresolved path, bad property or value) are listed with their index and reason, and the rest still apply. Prefer it over repeated set_property calls, since Roblox limits the plugin to about 500 requests a minute. For attributes use mass_set_attribute.

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": {
      "edits": "<edits>"
    },
    "name": "mass_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
editsYesOne entry per change. The same path may appear several times.
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / edits / description
      Added value: +"One entry per change. The same path may appear several times."
    • addedInput schema / properties / edits / items / properties / name / description
      Added value: +"Property name"
    • addedInput schema / properties / edits / items / properties / path / description
      Added value: +"Instance to change. 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)\"."
    • addedInput schema / properties / edits / items / properties / value / description
      Added value: +"New value. Write a primitive (string, number, boolean) or a typed wrapper: {Vector3:[x,y,z]}, {Color3:[r,g,b]} (0-1), {UDim2:[xScale,xOffset,yScale,yOffset]}, {CFrame:[x,y,z] or all 12 components}, {EnumItem:\"Enum.Material.Wood\"}, {BrickColor:\"Bright red\"}."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds substantive behavior: edits are applied atomically as one undo step yet validated independently, failures are reported with index and reason while the rest still apply, and there is a ~500 requests/minute throttle. Partial-success semantics and the undo grouping are exactly the operational facts an agent needs and cannot infer from the annotations.

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 core action, then failure semantics, then alternative routing. Every clause earns its place — no restating of the name or title and no filler.

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?

For a batch mutation with no output schema, the description covers everything an agent needs: scope, partial-failure reporting format (index plus reason), undo behavior, rate limiting, and the sibling to use for attributes. Nothing material is left implicit.

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% and the schema already documents path format, typed value wrappers, and the place fallback in detail. The description adds only indirect meaning — that failures are indexed back to edit entries — but no new syntax or constraints beyond the schema. Baseline 3 is appropriate when the schema carries the parameter burden.

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 ('apply many property changes') plus scope ('across any number of instances, in one call recorded as one Studio undo step'), which immediately separates it from set_property and mass_set_attribute. An agent knows exactly what operation this performs without opening the 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: 'Prefer it over repeated set_property calls' with the reason (Roblox limits the plugin to about 500 requests a minute) and a clear exclusion ('For attributes use mass_set_attribute'). Both the when and the when-not are named with the selecting condition.

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