Roblox MCP

Overview Schema Source Related Servers Discussions Admin

manage_sync

Manage sync for the current place: view status, change history, and sync directions; read and write synced files; monitor real-time progress and bandwidth.

Instructions

[PRO] Project sync management: status, history, direction settings, read/write synced files.

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": {
      "action": "<action>"
    },
    "name": "manage_sync"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	[PRO] Sync action. status_current_place: get sync status for the current connected place. history: get change history. directions: get per-type sync directions. read_file: read a synced file. write_file: write to a synced file. progress: get real-time sync progress and bandwidth.
`placeId`	No	Place ID for sync operations. Used by: history, directions, read_file, write_file.
`instancePath`	No	Instance path for file read/write. Used by: read_file, write_file.
`content`	No	File content to write. Used by: write_file.
`query`	No	Query parameters for history. Used by: history.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.7.5May 12, 2026

changedInput schema / properties / action / description

Previous value: -"[PRO] Sync action. status: get sync status for a place. config: get sync configuration. history: get change history. directions: get per-type sync directions. read_file: read a synced file. write_file: write to a synced file. progress: get real-time sync progress and bandwidth."New value: +"[PRO] Sync action. status_current_place: get sync status for the current connected place. history: get change history. directions: get per-type sync directions. read_file: read a synced file. write_file: write to a synced file. progress: get real-time sync progress and bandwidth."

changedInput schema / properties / action / enum

Previous value: -[
-  "status",
-  "config",
-  "history",
-  "directions",
-  "read_file",
-  "write_file",
-  "progress"
-]New value: +[
+  "status_current_place",
+  "history",
+  "directions",
+  "read_file",
+  "write_file",
+  "progress"
+]

changedInput schema / properties / placeId / description

Previous value: -"Place ID for sync operations. Used by: status, config, history, directions."New value: +"Place ID for sync operations. Used by: history, directions, read_file, write_file."

First observedv2.0.1Mar 24, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects, authentication requirements, rate limits, or what happens during read/write operations. It only outlines basic functionality without deeper context.

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?

The description is very concise, consisting of a single sentence. However, it lacks structure: it is not front-loaded, and the colon-separated list could be clearer. It is minimally acceptable but not well organized for quick scanning.

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?

Despite high schema coverage, the tool is complex with multiple actions, a nested query object, and no output schema. The description does not explain return values, action-specific details, or required parameters (e.g., placeId for certain actions). It is incomplete for a tool of this complexity.

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%, so the input schema already documents all parameters. The description summarizes the actions but adds little new meaning beyond the schema. Baseline of 3 is appropriate as the description does not significantly enhance parameter understanding.

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 clearly specifies that the tool manages project sync, listing key actions (status, history, direction settings, read/write synced files). It distinguishes from sibling tools (e.g., manage_animation) by focusing on sync functionality. However, it does not explicitly differentiate from siblings.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context, or when not to use it. Sibling tools exist for different domains, but no explicit usage guidance is given.

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