Skip to main content
Glama

manage_properties

Modify Roblox instance properties, attributes, and tags to configure game objects and automate development workflows.

Instructions

Get/set properties, attributes, and tags on instances. [PRO] set_calculated, set_relative, mass_set, mass_get, modify_children.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesProperty action. Basic: get, set, get_all, set_multiple, get_attr, set_attr, get_all_attrs, delete_attr, add_tag, remove_tag, check_tag, get_tags, get_tagged. [PRO]: set_calculated, set_relative, mass_set, mass_get, modify_children.
pathNoInstance path. Used by: get, set, get_all, set_multiple, get_attr, set_attr, get_all_attrs, delete_attr, add_tag, remove_tag, check_tag, get_tags, set_calculated, set_relative.
propertyNoProperty name (e.g., "Size", "Position", "Anchored"). Used by: get, set.
valueNoValue to set. Supports primitives, Vector3 {x,y,z}, Color3 {r,g,b} (0-255), CFrame (12-number array), UDim2 {xScale,xOffset,yScale,yOffset}, Enum strings. Used by: set, set_attr, set_relative.
propertiesNoDictionary of property names to values. Used by: set_multiple.
attributeNoAttribute name. Used by: get_attr, set_attr, delete_attr.
tagNoTag string (case-sensitive). Used by: add_tag, remove_tag, check_tag.
tagNameNoTag to search for. Used by: get_tagged.
rootNoRoot path to filter get_tagged results. Used by: get_tagged.
maxResultsNoMaximum results for get_tagged. Default: 100.
expressionNo[PRO] Mathematical expression to evaluate. Used by: set_calculated. Example: "baseValue * multiplier".
variablesNo[PRO] Variable name to value/path mapping. Used by: set_calculated. Example: {"baseValue": "workspace.Config.BaseValue", "multiplier": 2}.
operationNo[PRO] Mathematical operation for relative property change. Used by: set_relative.
amountNo[PRO] Value for relative operation. Can be number, Vector3, etc. Used by: set_relative. Alias for value in set_relative context.
pathsNo[PRO] Array of instance paths for bulk operations. Used by: mass_set, mass_get.
parentPathNo[PRO] Parent path whose children will be modified. Used by: modify_children.
modificationsNo[PRO] Properties to set on children. Used by: modify_children. Contains propertyName, propertyValue, filter, recursive.
propertyNameNo[PRO] Property name for mass operations or set_calculated/set_relative. Used by: mass_set, mass_get, set_calculated, set_relative, modify_children.
propertyValueNo[PRO] Property value for mass_set and modify_children.
filterNo[PRO] Class name filter for modify_children.
recursiveNo[PRO] Modify all descendants, not just immediate children. Used by: modify_children. Default: false.
includeReadOnlyNoInclude read-only properties. Used by: get_all. Default: false.
Behavior2/5

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

No annotations provided, yet the description fails to disclose mutation risks, side effects, or safety considerations for destructive actions (delete_attr, remove_tag, set operations). The '[PRO]' label is mentioned but not explained (authorization tier, feature flags, etc.).

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?

Single efficient sentence covers core functionality. The '[PRO]' appendix is slightly awkward but informative. No wasted words, though front-loading could better prioritize the scope distinction from siblings.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Thin for 22-parameter complexity. No output schema is present, yet description doesn't clarify return values or structure. PRO feature explanation absent. Relies heavily on the excellent schema documentation, leaving conceptual gaps for an AI selecting between 20+ sibling tools.

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 excellent inline documentation ('Used by: X'). Description lists PRO action names but adds no semantic value beyond the schema—does not explain what 'set_calculated' or 'modify_children' conceptually do.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb-resource combination ('Get/set properties, attributes, and tags on instances') that identifies the specific targets. Distinguishes somewhat from siblings like 'mutate_instances' by focusing on property/tag manipulation rather than structural changes, though explicit differentiation is absent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

Provides no guidance on when to select this tool versus siblings like 'mutate_instances', 'query_instances', or 'workspace_state'. Does not mention prerequisites for PRO features or when to use basic vs. advanced actions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hope1026/roblox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server