Skip to main content
Glama

Change a scene

update_scene
Idempotent

Change a scene's title, its script or both. The script is what the recorder's teleprompter shows (the words to say, not stage directions). Free. Returns the scene.

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": {
      "project_id": "<project_id>",
      "scene_id": "<scene_id>"
    },
    "name": "update_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
scriptNoReplaces the scene's script: the words the teleprompter shows while the person records: what to say, not stage directions
scene_idYesFrom get_project
project_idYesFrom create_project

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotent, non-destructive, non-read-only behavior. The description adds real value beyond them: the script field is a full replacement, it is what the teleprompter displays (spoken words, not stage directions), the operation is free, and the updated scene is returned.

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?

Three short sentences, front-loaded with the mutation targets, then a clarifying gloss on script, then cost and return. Nothing is wasted.

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

Completeness4/5

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

For a small two-field mutation with annotations covering the safety profile and a stated return value, this is close to complete. Minor gaps: behavior when scene_id is invalid and whether omitting a field leaves it untouched (only implied).

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 75% and the schema already documents script semantics and where project_id/scene_id come from. The description mostly restates the script definition, though its 'title, script or both' phrasing usefully signals that both editable fields are optional.

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 and resource plus the exact fields touched: 'Change a scene's title, its script or both.' That distinguishes it from add_scene (creation) and from the promo/short/graphic updaters, though it never names a sibling explicitly.

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?

Implies usage (modify an existing scene, not create one) and the 'Free' note hints that cost-conscious alternatives exist, but there is no explicit when-to-use/when-not guidance or named alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources