BlitzReels Video Editor

Get Generation Plan Brief

generation_plan_brief

Read-onlyIdempotent

Read a generation brief from rawPrompt. Source-video edits return execution for generation_video_create with required assets and transformation controls. New scenes return an authoring grammar and planJsonSchema for generation_plan_validate. The video creation provenance.originalRequest field retains rawPrompt when supplied. This read does not generate media or spend credits.

Input Schema

Name	Required	Description	Default
`genre`	No	Genre pack id (e.g. pixar-culture-skit). The brief lists available ids in availableGenres; the pack's beats and visual contract override the generic grammar.
`rawPrompt`	No	Original request. Clone or character-replacement requests select a video transformation brief instead of a new-story plan.
`aspectRatio`	No		9:16
`visualStyle`	No	Visual style preset id; its locked style contract is included in the brief.
`videoModelId`	No	Target video model id (see generation_options_list, kind: video). Defaults to the strongest single-take model.
`targetDurationSeconds`	No	Desired final video duration in seconds.

Output Schema

Name	Required	Description	Default
`brief`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 21, 2026

addedInput schema / properties / rawPrompt

Added value: +{
+  "description": "Original request. Clone or character-replacement requests select a video transformation brief instead of a new-story plan.",
+  "maxLength": 5000,
+  "type": "string"
+}

addedOutput schema / properties / brief / properties / execution

Added value: +{
+  "description": "Source-video operation, model and required assets; null for new-story plans.",
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed3 schema fields changedAug 12, 2026

addedInput schema / properties / genre

Added value: +{
+  "description": "Genre pack id (e.g. pixar-culture-skit). The brief lists available ids in availableGenres; the pack's beats and visual contract override the generic grammar.",
+  "type": "string"
+}

addedOutput schema / properties / brief / properties / availableGenres

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / brief / properties / genrePack

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

AddedAug 10, 2026

TDQS

A3.8/5.0

Behavior4/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 genuinely new behavioral context: no media is generated and no credits are spent, plus the provenance.originalRequest retention note. The latter sentence is oddly phrased and hard to parse, which costs a point.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The mode-routing information is front-loaded, but the sentence "The video creation provenance.originalRequest field retains rawPrompt when supplied" is dense, jargon-laden and does not help an agent decide or invoke correctly. The description reads as five compressed statements rather than a clean, prioritized explanation.

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?

An output schema exists and annotations cover the safety profile, so the description need only establish the routing logic and cost profile — both of which it does. Minor gap: no stated prerequisites for the genre/visualStyle presets referenced by the parameters.

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 83%, so the schema already documents genre, visualStyle, videoModelId, aspectRatio and duration thoroughly. The description adds meaning mainly for rawPrompt (source-video/transformation vs. new-story branching), but that same branching is already stated in the schema's rawPrompt description, so the added value is marginal.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource is explicit ("Read a generation brief from rawPrompt") and the description distinguishes the two output modes and names the downstream consumers generation_video_create and generation_plan_validate. What a "brief" actually is remains somewhat abstract jargon, so it falls just short of a fully self-evident purpose.

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

Usage Guidelines4/5

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

The description makes the workflow position clear: this is the read/planning step whose output feeds generation_video_create (edits) or generation_plan_validate (new scenes). It does not state explicit "do not use when" conditions or required preconditions (e.g., must a genre pack exist first), which keeps it below a 5.

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

All BlitzReels Video Editor tools Inspect

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

Need Help?