Skip to main content
Glama

Save a season plan

autoshort_save_season_plan
DestructiveIdempotent

Saves, reviews and confirms a whole series season before any episode is produced, locking characters, narrator voice, style and episode cliffhangers into one approved plan.

Instructions

Design, review and confirm the WHOLE season of a series before any episode is made. Free (no credits). Founder rules: a series is fully designed and reviewed before any video is produced, and its characters, voice and style are fixed in every episode. Three steps, one tool: (1) pass plan to save it (version 1: logline, genre, language, narratorVoiceId, styleTokens, characters[] with look, sheetId and wardrobeLock, rules[], at least 3 episodes[] with title, characterName, cliffhangerLine and shots[] or a script). Every edit clears the review and the confirmation. (2) pass review: true (with or without plan) to run the season review: a deterministic checklist (cliffhangers, hooks, one narrator and style, no on-screen text, one subject per look and per shot, outfit locked, season price) plus an advisory AI review that lists up to 8 concrete issues; if the AI review cannot run the answer says so and the checklist stands. (3) show the owner the checklist, the AI issues and the season price, and ONLY after they say yes call again with confirm: true and planHash from the review. Every character an episode uses needs a READY sheet of this series (autoshort_create_character_sheet, one sheet per character) whose id is in the plan. Then autoshort_quote_character_episode / autoshort_create_character_episode make the planned episodes.

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": {
      "seriesId": "<seriesId>"
    },
    "name": "autoshort_save_season_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNoThe whole season plan. Omit to review or confirm the stored one.
reviewNoRun the season review on the stored plan (after saving `plan` if given).
confirmNoThe owner confirms the reviewed plan. Needs planHash; do not send `plan` in the same call.
aiReviewNoWith review: also run the advisory AI review (default true).
planHashNoWith confirm: the planHash the review returned.
seriesIdYesA series id from autoshort_list_series.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the supplied annotations: it states the call is free (no credits), that "every edit clears the review and the confirmation" (the concrete destructive consequence behind destructiveHint=true), that the deterministic checklist stands if the advisory AI review cannot run, and that the AI review caps at 8 concrete issues. It also discloses the review's output contents (checklist, issues, season price) even though no output schema exists.

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?

Purpose is front-loaded and the three modes are numbered and sequenced, which suits a multi-step tool. It is a single dense paragraph, however, and the parenthetical enumeration of plan fields duplicates what the schema already declares, adding length without new information.

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 six-parameter tool with deeply nested objects and no output schema, the description covers what an agent needs: required inputs per step, the review's return contents, failure-mode behavior, the confirmation gate, and the downstream dependency on character sheets. Nothing material about invoking it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns a point for adding cross-parameter semantics the schema cannot express, notably that `planHash` comes from the review response and that `confirm` must not be combined with `plan`. It does restate the plan's field list (logline, genre, language, characters, episodes), which duplicates the schema rather than adding meaning.

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?

Opens with a specific verb-and-resource pairing: "Design, review and confirm the WHOLE season of a series before any episode is made." It is immediately distinguishable from siblings like autoshort_get_season_plan (read), autoshort_plan_drama_season (drafting) and autoshort_create_character_episode (production). The three numbered modes (save / review / confirm) make the tool's composite identity explicit.

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?

Provides a full ordered workflow with explicit conditions: step 3 says to call with `confirm: true` "ONLY after they say yes" and requires the `planHash` from the review. It also names prerequisites and successors by name (autoshort_create_character_sheet must yield a READY sheet before episodes; autoshort_quote_character_episode / autoshort_create_character_episode consume the result). When-not guidance is present in the form of sequencing constraints.

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