Roblox MCP

by hope1026

Overview Schema Related Servers Score Discussions

Local

manage_scripts

Read, write, create, delete, and edit lines in script source code. Search and replace text across scripts.

Instructions

Manage script source code: read, write, create, delete, edit lines, search. [PRO] replace across scripts.

Input Schema

TableJSON Schema

Name	Required	Description
`action`	Yes	Script action. Basic: get_source, set_source, create, delete, edit_replace, edit_insert, edit_delete, search, get_dependencies. [PRO]: replace.
`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 script instance. Used by: get_source, set_source, delete, edit_replace, edit_insert, edit_delete, search, get_dependencies, replace.
`source`	No	Script source code. Used by: set_source (required), create (optional initial source).
`scriptType`	No	Type of script to create. Used by: create.
`parent`	No	Parent path for new script. Used by: create.
`name`	No	Name for new script. Used by: create.
`startLine`	No	Starting line number, 1-based inclusive. Used by: edit_replace, edit_delete.
`endLine`	No	Ending line number, 1-based inclusive. Used by: edit_replace, edit_delete.
`newLines`	No	New content to replace specified lines. Used by: edit_replace. Can be multi-line.
`lines`	No	Content to insert after afterLine. Used by: edit_insert. Can be multi-line. Alias for content.
`afterLine`	No	Line number after which to insert. Used by: edit_insert. Use 0 to insert at beginning.
`content`	No	Content to insert. Used by: edit_insert. Can be multi-line.
`pattern`	No	Search pattern (plain text or Lua pattern). Used by: search, replace.
`replacement`	No	[PRO] Replacement text. Used by: replace.
`caseSensitive`	No	Case-sensitive search. Used by: search. Default: false.
`wholeWord`	No	Match whole words only. Used by: search. Default: false.
`usePattern`	No	Treat pattern as Lua pattern instead of plain text. Used by: search, replace. Default: false.
`dryRun`	No	[PRO] Show what would be replaced without making changes. Used by: replace. Default: false.
`maxResults`	No	Maximum results to return. Used by: search. Default: 100.

Tool Definition Quality

B3.1/5.0

Behavior2/5

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

Without annotations, the description carries full burden for behavioral disclosure. It lists actions but does not mention side effects, destructive potential, or whether changes are reversible. The agent cannot infer safety or mutation scope from the description alone.

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

Conciseness5/5

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

The description is a single, well-structured sentence that lists key actions and highlights the PRO feature. Every word adds value, and no extraneous information is present. This is exemplary conciseness.

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?

Given the complexity (22 parameters) and lack of output schema, the description is minimal but adequate when combined with the exhaustive schema. It does not explain the dispatcher nature of the action parameter or the structure of results, leaving gaps for an agent to discover via schema.

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?

With 100% schema description coverage, the description adds no extra meaning to parameters. Baseline 3 is appropriate since the schema already documents the purpose of each parameter and ties them to actions.

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 states the tool manages script source code and lists specific actions (read, write, create, delete, etc.), distinguishing it from sibling tools like execute_luau. However, it does not explicitly cover all actions (e.g., get_dependencies) without referencing 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 Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., execute_luau for running scripts). The only usage hint is the PRO feature marker, but no context or exclusion criteria are provided.

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

Install Server

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

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