Skip to main content
Glama

Quote a character episode

autoshort_quote_character_episode
Read-onlyIdempotent

Price a planned 12–60 second episode from a confirmed season plan without spending credits. Returns the shot breakdown and exact credit cost so you can review before creating.

Instructions

Price one PLANNED episode (12-60 seconds, 3-8 shots) of a series with a confirmed season plan, starring the character the plan names. FREE: it spends nothing and starts nothing. Returns the shot plan (narration, action, camera and seconds of every shot), the exact credits (clips are Seedance at the per-second rate of the chosen resolution: 480p by default, 720p only when quote.pricePerResolution lists it as available, plus a still per shot and the narration), and a ready-made nextAction for autoshort_create_character_episode. Show the customer the price and the shots, and call the create tool only after they say yes. The same safety checks as the real call run here: real or famous people, anyone who looks under 18, sexual content and protected characters are refused with CONTENT_POLICY. Only an episode of a REVIEWED, CONFIRMED season plan can be quoted or made: send its script or shots exactly as planned (autoshort_get_season_plan). Without a confirmed plan the answer is SEASON_PLAN_REQUIRED or SEASON_NOT_REVIEWED, and for shots that are not a planned episode EPISODE_NOT_IN_PLAN, each with a nextAction. The narrator voice, the language, the style and the character come from the plan and cannot be overridden (SEASON_FIELD_LOCKED); to change an episode, edit the plan (that clears the review).

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_quote_character_episode"
  }
}

Input Schema

NameRequiredDescriptionDefault
shotsNoShots you write yourself (better pictures than the automatic split). Give `shots` OR `script`.
titleNoOptional title.
scriptNoThe narration, about 29-138 words. The system splits it into shots by sentence. Give `script` OR `shots`.
sheetIdNoOmit it: the character sheet is the one the season plan names for this episode. If given it must equal that sheet.
languageNoOmit it: the narration language is the season plan's. If given it must equal the plan's.
seriesIdYesA series id from autoshort_list_series whose season plan is reviewed and confirmed.
shotCountNoWith `script`: how many shots to split it into. Omit for an automatic count.
resolutionNoClip resolution. Default '480p'. '720p' costs more per second (see quote.pricePerResolution) and is only accepted when it is listed as available there; the quote and the create must use the same resolution.

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?

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds substantial context beyond them: it is free, it runs the same CONTENT_POLICY safety checks as the real call, and it enumerates failure modes (SEASON_PLAN_REQUIRED, SEASON_NOT_REVIEWED, EPISODE_NOT_IN_PLAN, SEASON_FIELD_LOCKED) each with a nextAction. It also discloses what the response contains (shot plan, exact credit breakdown, ready-made nextAction).

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?

Front-loaded with the core action and the free/paid distinction, then pricing, then errors. It is one dense paragraph and the error-code chain is compressed, but nearly every sentence carries actionable information for the agent.

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 an 8-parameter pricing tool with no output schema, the description covers what is returned, how credits are computed, what is refused, what prerequisites gate the call, and what to do next. Nothing an agent needs in order to call this correctly and interpret the result 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 baseline would be 3, but the description adds real meaning: the plan locks narrator voice, language, style, and character so language/sheetId cannot be overridden, resolution pricing depends on quote.pricePerResolution and must match the create call, and shots versus script is an either/or. It does not individually clarify every parameter (e.g., title, shotCount), so a 4 rather than 5.

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: 'Price one PLANNED episode (12-60 seconds, 3-8 shots) of a series with a confirmed season plan.' It also draws the boundary against the sibling that actually spends money by explicitly naming autoshort_create_character_episode and stating this tool 'spends nothing and starts nothing.'

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 workflow: 'Show the customer the price and the shots, and call the create tool only after they say yes,' and 'to change an episode, edit the plan.' Prerequisites are stated (a REVIEWED, CONFIRMED season plan via autoshort_get_season_plan) along with the exact conditions that make the call fail, so there is no ambiguity about when to invoke this versus create.

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