Roblox MCP

by hope1026

Overview Schema Source Related Servers Discussions Admin

Local

manage_animation

Load, play, stop, and list animation tracks on a Humanoid or AnimationController in Roblox Studio.

Instructions

[PRO] Animation: load, play, stop animations. Get animation tracks from humanoid/controller.

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_animation"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	[PRO] Animation action. load: load an animation on a Humanoid/AnimationController. play: play a loaded animation track. stop: stop a playing animation. get_tracks: list all loaded animation tracks.
`contextId`	No	Optional execution context identifier. Used to continue an existing context for mutating actions.
`contextSummary`	No	Optional structured execution context attached to this tool call.
`replayMetadata`	No	Optional replay-ready metadata attached to this tool call.
`path`	No	Path to the Humanoid, AnimationController, or Model containing one. Used by: load, play, stop, get_tracks.
`animationId`	No	Roblox animation asset ID (e.g., "rbxassetid://1234567"). Used by: load.
`trackId`	No	Animation track identifier returned by load. Used by: play (required), stop (required).
`speed`	No	Playback speed multiplier. Used by: play. Default: 1.
`fadeTime`	No	Fade time in seconds when starting/stopping. Used by: play, stop. Default: 0.1.
`weight`	No	Animation weight (0-1) for blending. Used by: play. Default: 1.
`priority`	No	Animation priority. Used by: play.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.7.5May 12, 2026

addedInput schema / properties / contextId

Added value: +{
+  "description": "Optional execution context identifier. Used to continue an existing context for mutating actions.",
+  "type": "string"
+}

addedInput schema / properties / contextSummary

Added value: +{
+  "description": "Optional structured execution context attached to this tool call.",
+  "properties": {
+    "affectedAreas": {
+      "items": {
+        "properties": {
+          "kind": {
+            "enum": [
+              "script",
+              "instance",
+              "property",
+              "system",
+              "gameplay",
+              "ui",
+              "terrain",
+              "lighting",
+              "asset",
+              "other"
+            ],
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "target": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "kind",
+          "target",
+          "label"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "expectedBehavior": {
+      "type": "string"
+    },
+    "intent": {
+      "type": "string"
+    },
+    "observedBehavior": {
+      "type": "string"
+    },
+    "testScenario": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / replayMetadata

Added value: +{
+  "description": "Optional replay-ready metadata attached to this tool call.",
+  "properties": {
+    "artifactRefs": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "assertionRefs": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "inputRefs": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "mode": {
+      "type": "string"
+    },
+    "seed": {
+      "type": "number"
+    },
+    "setupRefs": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "timeout": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedv2.0.1Mar 24, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only lists actions without mentioning side effects, permissions, error conditions, or whether operations are destructive. For a tool that loads and plays animations, this is a significant gap.

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?

The description is a single sentence that efficiently lists key actions. It is front-loaded with '[PRO]' and the word 'Animation'. While slightly minimal, it contains no unnecessary words and is easy to parse.

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?

Given 11 parameters, nested objects, and no output schema, the description is too brief. It omits return values, error handling, prerequisites (e.g., a valid Humanoid), and behavioral context. Users cannot assess completeness without inspecting schema further.

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 detailed descriptions for each parameter. The tool description adds no extra meaning beyond the schema. According to guidelines, baseline 3 is appropriate when schema does the heavy lifting.

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?

The description clearly states the tool's purpose: load, play, stop animations, and get animation tracks. It explicitly lists the main actions and the target (humanoid/controller), effectively distinguishing it from sibling tools like manage_audio or manage_camera.

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?

No explicit when-to-use or when-not-to-use guidance is provided. However, sibling tools cover distinct domains, so the usage context is implied. The description lacks guidance on choosing between actions, but the input schema's detailed action descriptions compensate partially.

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