Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_export

Exports a specified Roblox instance to an .rbxm file so you can save, back up, or share that object outside Studio.

Instructions

Export instance to .rbxm file (0600).

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": {
      "instance_path": "<instance_path>"
    },
    "name": "roblox_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputNo
instance_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does not say whether an existing file is overwritten, what happens when output is empty, whether the instance snapshot is read-only or affects the live session, or what "(0600)" refers to (presumably file permissions, but this is a guess).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence and front-loaded correctly, so nothing is wasted. However, the cryptic parenthetical makes it under-specified rather than efficient, and a few more words would have paid for themselves.

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

Completeness2/5

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

An output schema exists so return values need not be explained, but with no annotations and zero parameter documentation, key behavior for a file-writing operation is missing. For a two-parameter mutation/export tool this is too thin to call complete.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters. The description implies a file is produced but never explains the `output` parameter (including what the empty default means) or the format expected for `instance_path`, so it does not compensate for the schema gap.

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?

The description names a specific verb and resource ("Export instance") and the concrete output format (a .rbxm file), which distinguishes it from the sibling roblox_import. The trailing "(0600)" is unexplained and adds ambiguity rather than clarity.

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?

There is no statement of when to use this over alternatives such as roblox_backup or roblox_capture, nor any prerequisites. The agent must infer the use case entirely from the name and the word "export".

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