Skip to main content
Glama

set_props

Update properties, attributes, and CollectionService tags on one instance, multiple paths, or all instances sharing a tag in Roblox Studio, with undoable changes.

Instructions

Set properties, attributes, and/or CollectionService tags on one instance (path), several (paths), or all instances with a tag. Supports: Size:[2,3,4], Color:[255,0,0] or "#ff0000", Material:"Neon", CFrame:[x,y,z] or [x,y,z,rx,ry,rz] (deg), UDim2:[xs,xo,ys,yo], Rect:[x0,y0,x1,y1], ColorSequence:["#f00","#00f"], NumberSequence:[0,1], Font:"GothamBold", PhysicalProperties:[d,f,e], {"Enum":"Material.Neon"}, {"ref":"Workspace.Other"}, {"nil":true}. Undoable.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_props"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoUpdate every instance having this CollectionService tag.
pathNoSingle target instance path.
tagsNoArray of tags to add, or {"add":[...], "remove":[...]}.
pathsNoMultiple target instance paths.
propsNo
studioNoOptional. Target Studio (name substring, place id or id). Only needed when several Studios are open and none was selected.
attributesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does disclose meaningful traits: the operation is undoable, accepts multiple targeting scopes, and coerces value encodings in specific ways (degrees for CFrame rotations, hex vs array colors, enum/ref/nil sentinels). It does not say whether properties merge or are replaced, or what happens on an unknown property name or an unresolvable path.

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 targeting modes are front-loaded, followed by a dense but high-value format catalogue; nearly every token earns its place because the value encodings are non-obvious. The single run-on sentence makes it harder to scan than a short bulleted structure would, but nothing is redundant.

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 7-parameter mutation tool with nested objects, no annotations, and no output schema, the definition covers targeting, value encoding, and undoability — the main things an agent needs to call it correctly. The remaining gap is failure/merge semantics (overwrite vs additive behavior for `props`/`attributes`, error behavior on bad paths), which matters for a write tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 71%, and the description compensates well for the weakest spot: `props` is an undescribed free-form object in the schema, and the description supplies a detailed encoding guide (Size, Color, Material, CFrame with degree units, UDim2, Rect, ColorSequence, NumberSequence, Font, PhysicalProperties, Enum/ref/nil wrappers). It does not distinguish `props` from `attributes`, nor expand on `studio` beyond what the schema already says.

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?

Opens with a specific verb and resource ("Set properties, attributes, and/or CollectionService tags") and immediately enumerates the three targeting modes (single `path`, multiple `paths`, tag-wide). An agent can tell exactly what this tool mutates and at what scope 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use it (whenever you need to write properties/attributes/tags to instances) and explains the `studio` targeting caveat for multi-Studio sessions. However it gives no explicit routing guidance against siblings such as `script_edit` for code or `inspect` for reading, and states no preconditions or when-not-to-use cases.

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