Skip to main content
Glama

Edit the video direction and render settings

update_video_direction
Idempotent

Change the creative plan and render settings for a product's upcoming video before generation. Only the fields you provide are updated, preserving current values.

Instructions

Edit the creative direction and render settings for a product's next video. Only the fields you pass are changed; everything else keeps its current value.

creative_direction is the plan the render is built from. It is free text, but the drafts follow a six-section shape that works well and is worth preserving when editing:

Hook: ... Content Focus: ... Format: ... Execution Guidelines: ... Strict Guidelines & Restrictions: ...

Do not invent a direction from nothing when one has not been drafted yet — call redraft_video_direction and edit what comes back. Leaving it empty is also valid: generation works without a direction.

creator_note is different and smaller: the user's own short note to the director ("mention it is machine washable", "for Father's Day"). It is carried through to the render verbatim, so put the user's words in it, not your paraphrase.

Only works before generation starts. This does not spend credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ratioNoAspect ratio. 9:16 (vertical) is the default and what social feeds want.
product_idYesThe product's id.
resolutionNo1080P needs a paid plan; a pick above the plan's ceiling quietly becomes that ceiling (the response reports what was actually saved).
creator_noteNoThe user's short note to the director, max 1000 characters.
enable_audioNoWhether the render has sound.
target_marketNoFree text, e.g. "US/North America" or "Japan". Drives the spoken language unless one is set explicitly. Saved on the brand, so it carries to later videos.
creative_directionNoThe full creative plan, max 3000 characters. Pass an empty string to clear it.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark this as non-read-only and non-destructive, but the description adds rich behavioral context: partial updates only, no credit spending, the pre-generation precondition, creator_note being passed verbatim, and target_market persisting on the brand. This goes well beyond the structured hints and does not contradict them.

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

Conciseness5/5

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

The description is front-loaded with the core action and partial-update semantics, then groups parameter guidance by relevance. It is longer than average, but the tool has seven parameters and subtle constraints; no sentence is filler, and key warnings (don't invent, only before generation, no credits) are clearly highlighted.

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 7-parameter mutation tool with no output schema, the description covers the essential invocation context: what changes, when it is valid, cost behavior, parameter-specific quirks, and the relationship to redraft_video_direction. Nothing critical needed to call it correctly appears missing.

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

Parameters5/5

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

Schema description coverage is 100%, but the description adds substantial meaning: the six-section creative_direction structure, the instruction not to invent a direction and to prefer redraft_video_direction, creator_note's verbatim pass-through semantics, and target_market's lasting brand-level effect. This materially helps an agent fill parameters correctly.

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?

The description opens with a specific verb and resource: 'Edit the creative direction and render settings for a product's next video.' It also distinguishes itself from the closest sibling by calling out redraft_video_direction explicitly, so an agent can identify the right tool without ambiguity.

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 explicit routing guidance: use redraft_video_direction when no direction has been drafted yet, and states the timing constraint 'Only works before generation starts.' It also explains what is deliberately not done here ('does not spend credits'), which helps the agent choose between this and generation tools.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/InstantStudioAI/instantclips-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server