InstantClips

Edit the video direction and render settings

update_video_direction

DestructiveIdempotent

Edit the next video's creative_direction, its idea (creator_note), settings and photos; only the fields you pass change. Settings are parameters, not direction text. A new idea, length or ratio rewrites the direction: poll get_product.

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": {
      "product_id": "<product_id>"
    },
    "name": "update_video_direction"
  }
}

Input Schema

Name	Required	Description
`ratio`	No	Aspect ratio; 9:16 suits social feeds. A change rewrites an existing direction, unless creative_direction comes too.
`product_id`	Yes	The product's id.
`resolution`	No	720P and 1080P need a credit pack or an eligible plan. A higher pick saves the account's ceiling; adjustments says so.
`creator_note`	No	One of ideas word for word, or the user's words (max 4000). Rewrites the direction unless creative_direction comes too.
`target_market`	No	Free text, e.g. "US/North America". Sets the spoken language, and is saved on the brand for its other products.
`duration_seconds`	No	Length in seconds, priced per second; the text never sets it. Above the plan's ceiling (free: 20) it saves that.
`creative_direction`	No	The full plan, max 6000 characters; edit the drafted one. Only its scenes make the video. Empty clears it.
`selected_image_ids`	No	Photos to render, in order, by get_product's image_id: usable ones, at most 9, held_back ones too. Empty: the default.

Output Schema

Name	Required	Description
`ratio`	No
`format`	No
`drafting`	Yes
`editable`	Yes
`next_step`	Yes
`affordable`	No
`product_id`	Yes
`resolution`	No
`adjustments`	No
`credit_cost`	Yes
`draft_error`	No
`creator_note`	No
`draft_failed`	Yes
`target_market`	No
`style_pictures`	No
`duration_seconds`	No
`look_description`	No	What the user's style pictures show, in words they can edit on the website: the setting, light, palette, mood and presenter the video takes its look from. Never a product.
`opened_new_video`	Yes
`video_request_id`	Yes
`creative_direction`	No
`selected_image_ids`	Yes
`style_picture_urls`	No	The style pictures, never filmed; each link lasts an hour.
`watermark_expected`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, so the description's job is to explain what gets destroyed and how — which it does: changing idea, length or ratio rewrites an existing direction, an empty creative_direction clears it, target_market is persisted on the brand and affects other products, and over-ceiling duration is silently clamped. These are real side effects not derivable from annotations. It stops short of saying whether a rewrite discards prior manual edits without warning, but the coverage is well above the annotation baseline.

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?

Three short, front-loaded clauses with no filler; the partial-update rule comes first and the side-effect warning follows. The telegraphic style ('settings and photos', 'poll `get_product`') is efficient but borders on cryptic, and backtick-referenced tool names inside prose slightly reduce scanability.

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?

For an 8-parameter mutation tool with a full output schema and rich parameter descriptions, the description covers the essentials: partial-update semantics, destructive rewrites, persistence side effects and the recommended follow-up call. The only real gap is routing against redraft_video_direction, which an agent choosing among siblings would want.

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%, and the per-parameter descriptions already carry the rewrite interactions, pricing and plan ceilings. The description adds one genuinely useful framing — 'Settings are parameters, not direction text' and 'only the fields you pass change' — but otherwise restates the same categories the schema documents. Baseline 3 is appropriate when the schema is doing this much work.

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?

States a specific verb and resource: editing the next video's creative_direction, idea (creator_note), settings and photos, plus the key scope rule that only passed fields change. An agent can tell this is a partial-update tool for a video direction. It never names or contrasts with the sibling redraft_video_direction, so the boundary against that alternative is left implicit.

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

Usage Guidelines3/5

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

Gives useful in-tool guidance: 'Settings are parameters, not direction text' and 'A new idea, length or ratio rewrites the direction: poll `get_product`' tell the agent the consequence and a follow-up step. However, there is no explicit when-to-use-this-versus-alternatives guidance — nothing says when to call redraft_video_direction instead, which is the most likely confusion given the sibling list.

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

All InstantClips 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.