Skip to main content
Glama

Plan a drama season

autoshort_plan_drama_season
Read-only

Draft a short-drama season from a one-line premise: get a character bible and 2–8 episode scripts with spoken cliffhangers, each sized for 12–60 seconds of narration.

Instructions

Drama Studio writers room: turn a one-line premise into a short-drama season: a character bible (1-4 original fictional characters: name, role, look) and 2-8 episode scripts, each with a title, a logline, a script and a "cliffhangerLine". The cliffhanger is SPOKEN: the script's last sentence is exactly "cliffhangerLine" (an open hook for every episode but the last; a payoff plus one lingering question for the last), the first sentence is a hook and the next episode picks the hook up. Each script is already sized to pass autoshort_quote_character_episode (12-60 seconds of narration); an episode that could not be made to fit comes back with needsEditing: true and the exact limit in issue. FREE: it spends no credits, starts nothing and saves nothing (it is limited per hour). Characters are always original fictional adults, animals, robots or mascots; real people, brands and sexual or graphic content are refused. Next steps: autoshort_create_series (paused) with the main character as characterDescription, autoshort_create_character_sheet, then autoshort_save_season_plan (the whole season: cast, voice, style, every episode), review it, get the customer's yes and confirm it; only then autoshort_quote_character_episode and autoshort_create_character_episode per episode.

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": {
      "premise": "<premise>",
      "genre": "<genre>",
      "episodes": "<episodes>"
    },
    "name": "autoshort_plan_drama_season"
  }
}

Input Schema

NameRequiredDescriptionDefault
genreYesdrama, thriller, comedy, horror or romance.
premiseYesThe story in one to three sentences: who, what they want, what goes wrong.
episodesYesHow many episodes.
languageNoLanguage code of the scripts, such as 'en' or 'vi'. Default 'en'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, but the description adds substantial context beyond them: it is FREE, spends no credits, starts nothing and saves nothing, and is rate-limited per hour. It also discloses failure semantics (needsEditing: true plus the exact limit in `issue` when a script cannot be sized to 12-60 seconds) and content-policy refusals, which an agent cannot infer from annotations.

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 purpose is front-loaded in the first clause, and nearly every sentence carries load (output shape, cliffhanger contract, sizing, cost, policy, next steps). The downside is a single dense paragraph of stacked clauses that is harder to scan than a bulleted sequence; a few phrases, such as restating the cliffhanger rule twice, could be tightened.

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?

There is no output schema, and the description compensates by naming the returned fields (character bible entries, per-episode title, logline, script, cliffhangerLine, needsEditing and `issue`). Given the tool's complexity — a generative, open-world planning step feeding a multi-tool pipeline — nothing essential for a correct first call 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 description coverage is 100%, so all four parameters are already documented, including the genre enum and language default. The description adds only light param-level meaning — that the premise is a one-line seed and that the episode count drives how many scripts come back — and never addresses `language` or the genre options, so the baseline of 3 applies.

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 concrete verb and resource — 'turn a one-line premise into a short-drama season' — and names the exact artifacts produced (a 1-4 character bible and 2-8 episode scripts with title, logline, script, cliffhangerLine). This is clearly distinguishable from siblings like autoshort_create_character_episode or autoshort_save_season_plan, which operate on already-planned material.

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?

Explicit sequencing guidance is given: after planning, use autoshort_create_series (paused) with the main character as characterDescription, then autoshort_create_character_sheet, then autoshort_save_season_plan, and only after customer confirmation autoshort_quote_character_episode and autoshort_create_character_episode. It also states exclusions — real people, brands, sexual or graphic content are refused — so the agent knows when this tool will not deliver.

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