Skip to main content
Glama

rename_scene

Idempotent

Change a scene's display name in the scene list and timeline by ID or index, with one undo step; fails if the scene is missing or the name is empty.

Instructions

Rename a scene (the name the person sees in the scene list and the timeline). Names don't have to be unique and change nothing else in the film. One undo step for the person. Fails if the scene isn't found or the name is empty. Returns { done }. Shots have no names; scenes are listed by get_project.

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": {
      "id": "<id>",
      "name": "<name>"
    },
    "name": "rename_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesScene id or index from 0 (get_project).
nameYesThe new name, like 'The chase'. Short is best; it can't be empty.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • changedInput schema / properties / id / description
      Previous value: -"Scene id or index."New value: +"Scene id or index from 0 (get_project)."
    • addedInput schema / properties / name / description
      Added value: +"The new name, like 'The chase'. Short is best; it can't be empty."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that only the label changes, that the operation is a single undo step for the user, the two failure conditions (scene not found, empty name), and the exact return shape { done }. Annotations cover safety/idempotency, and the description adds mutation scope and error semantics.

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?

Four tight sentences, front-loaded with the effect and followed by behavioral facts, with no filler. The trailing shot/get_project remark is slightly tangential but does help the caller find ids.

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

Completeness5/5

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

For a two-parameter mutation with no output schema, the description covers effect scope, undo behavior, failure modes, and the return value, so nothing an agent needs before calling is missing.

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%, so both parameters are already documented. The description adds mild value by noting non-uniqueness of names (so name cannot serve as an identifier) and by pointing to get_project as the source of ids, but adds no format or range detail beyond the schema.

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?

States a specific verb and resource ("Rename a scene") and immediately disambiguates which 'name' is meant — the label shown in the scene list and timeline. That distinguishes it from add_scene or any content-editing tool without needing the sibling schemas.

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?

Useful context is given (names need not be unique, nothing else changes, how to obtain scene ids via get_project), which implicitly tells the agent when this tool applies. However, there is no explicit when-not-to-use or named alternative for related operations such as renaming shots or moving scenes.

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