Skip to main content
Glama

rename_scene

Change the name of an existing OBS Studio scene to update your streaming or recording setup.

Instructions

Rename an existing scene.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scene_nameYesCurrent name of the scene.
new_nameYesNew name for the scene.

Implementation Reference

  • The 'rename_scene' tool handler invokes the OBS 'SetSceneName' method with the provided scene name and new name.
    case "rename_scene": {
      await obs.call("SetSceneName", {
        sceneName: args.scene_name,
        newSceneName: args.new_name,
      });
      return ok({ renamed: { from: args.scene_name, to: args.new_name } });
    }
  • The 'rename_scene' tool input schema definition, which requires 'scene_name' and 'new_name'.
    {
      name: "rename_scene",
      description: "Rename an existing scene.",
      inputSchema: {
        type: "object",
        properties: {
          scene_name: {
            type: "string",
            description: "Current name of the scene.",
          },
          new_name: {
            type: "string",
            description: "New name for the scene.",
          },
        },
        required: ["scene_name", "new_name"],
      },
    },
Behavior2/5

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

No annotations are provided, yet the description fails to disclose mutation side effects: whether references to the scene name are updated throughout the system, uniqueness constraints on 'new_name', or behavior when 'scene_name' does not exist. The agent knows only that a rename occurs, not how it fails or impacts other state.

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?

Extremely efficient at four words with no redundancy. However, given the lack of annotations and behavioral context, this brevity arguably underserves the agent's needs—efficient but potentially insufficient.

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?

For a mutation tool with zero annotations and no output schema, the description lacks critical operational context: success indicators, error conditions, or referential integrity guarantees. It meets only the absolute minimum definition of stating intent.

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 coverage is 100% with both parameters fully self-documented ('Current name', 'New name'). The description adds no validation rules, character limits, or format requirements beyond the schema, warranting the baseline score.

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?

States a specific verb (rename) and resource (scene) clearly. The word 'existing' implicitly signals this operates on current assets vs. creating new ones. However, it does not differentiate from sibling 'set_scene' (which likely activates a scene rather than renaming it).

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 use this versus alternatives like 'create_scene' or 'remove_scene', nor prerequisites such as scene existence verification. Offers no 'when-not-to-use' constraints.

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/LarsCanGit/OBS-MCP'

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