Skip to main content
Glama
Sign In

AutoShort

by org.autoshort
OverviewDiscussionsAdmin

autoshort_quote_character_episode

Read-onlyIdempotent

Price one PLANNED episode (30-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).

Input Schema

NameRequiredDescriptionDefault
shotsNoShots you write yourself (better pictures than the automatic split). Give `shots` OR `script`.
titleNoOptional title.
scriptNoThe narration, about 74-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 observed

TDQS

A4.6/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 adds substantial context: it spends nothing and starts nothing, runs the same safety checks as the real call (CONTENT_POLICY refusal categories), and enumerates failure modes with nextActions. This is rich behavioral disclosure beyond structured fields.

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 purpose and the free/paid distinction, and content is dense with little waste. However, it is a single long paragraph bundling workflow, error codes, safety policy, and field locking, which could be split for faster scanning.

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?

No output schema exists, but the description fully covers return values (shot plan, exact credits, ready-made nextAction) and all error outcomes, leaving nothing an agent needs to invoke and interpret it correctly.

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 coverage is 100%, so the schema already documents every parameter, including the script-vs-shots split and the locked sheetId/language fields. The description reinforces the locking constraint and resolution pricing rationale but adds little per-parameter syntax beyond what the schema states, so baseline 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 specific verb (price) and resource (one planned episode of a series with a confirmed season plan), including scope constraints like 30-60s / 3-8 shots. It explicitly names the create sibling it hands off to, so an agent can distinguish it from autoshort_create_character_episode without opening the schema.

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?

Gives explicit when-to-use and when-not: 'call the create tool only after they say yes,' plus error-routing conditions (SEASON_PLAN_REQUIRED, SEASON_NOT_REVIEWED, EPISODE_NOT_IN_PLAN, SEASON_FIELD_LOCKED) and the instruction to point to autoshort_get_season_plan for the plan. The workflow alternative is fully specified.

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

All AutoShort toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources