Skip to main content
Glama

storyline.update_scene

Edit a scene already accepted into the storyline path

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": {
      "projectId": "<projectId>",
      "sceneId": "<sceneId>",
      "edits": "<edits>"
    },
    "name": "storyline.update_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
editsYes
sceneIdYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a mutation but does not disclose side effects, whether edits affect downstream storyline state, whether accepted status is preserved, required permissions, or any failure behavior.

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 front-loaded sentence with no filler, and the key scope constraint appears immediately. It is concise, though its brevity is more a symptom of under-specification than efficient communication.

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

Completeness1/5

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

For a mutation tool with a nested edits object, no annotations, no output schema, and zero schema description coverage, the definition is far too thin. An agent cannot know what editing a storyline-accepted scene entails or which nested fields are meaningful from the description alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no meaning about projectId, sceneId, or the nested edits object containing seven fields. It does not explain which fields are editable, how partial edits behave, or what the nested object accepts beyond what the bare schema shows.

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 gives a specific verb and resource: "Edit a scene" and adds scope with "already accepted into the storyline path." It is distinguishable from generic scene creation or deletion, but it does not explicitly distinguish itself from the sibling scene.update or scenario tools.

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?

The phrase "already accepted into the storyline path" implies a precondition for use, suggesting the agent should only call this on accepted scenes. However, it names no alternatives and does not state what to use for unaccepted scenes or when to prefer scene.update instead.

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.