Skip to main content
Glama

Update a draft

update_draft
DestructiveIdempotent

Change a draft: its title and/or REPLACE all its scenes (1-12, each with scriptText and optional visualPrompt / durationSeconds). The narration you send is exactly what is spoken. To change one scene use revise_scene. Edits are screened like any prompt. Free; works only while the draft has not been rendered. Requires the "video:create" scope.

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": {
      "draftId": "<draftId>"
    },
    "name": "update_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
scenesNoThe complete new scene list (replaces the old one).
draftIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only flag destructiveHint/readOnlyHint/idempotentHint/openWorldHint; the description adds concrete behavioral facts an agent cannot get from them: the scene list is fully replaced rather than merged, the submitted narration is spoken verbatim, edits pass the same screening as prompts, the call is free, and it requires the 'video:create' scope. These are exactly the destructive/precondition/auth details the annotations do not spell out.

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?

It is front-loaded, with the core action and its replace semantics in the first clause, followed by routing, warnings, cost, and scope in descending priority. The parenthetical enumerating scene fields is somewhat redundant with the schema and the wording is dense, but no sentence is genuinely 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 destructive mutation with no output schema, the description covers replacement semantics, precondition, authorization scope, and cost. It stops short of saying what the response contains or whether existing scene identifiers survive a replacement, which are minor gaps for a tool this well annotated.

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 description coverage is only 33%, so the description has to carry weight; it partly does by restating the 1-12 scene range, the scriptText/visualPrompt/durationSeconds makeup, and the replace-not-merge semantics. However most of that duplicates text already present in the schema, and the required draftId remains entirely unexplained (no hint about where a draft ID comes from or what it identifies).

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?

The definition opens with a specific verb and resource ('Change a draft') and immediately scopes the operation to title and a full scene-list replacement. It also states the inverse case explicitly ('To change one scene use revise_scene'), so an agent can separate it from the sibling without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives the positive selection rule (title and/or full scene replacement), the alternative and when to prefer it (revise_scene for a single scene), a hard precondition (only while the draft has not been rendered), and a cost signal ('Free'). This is about as complete a routing instruction as a tool description gets.

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