InstantClips

Generate the video (spends credits)

generate_video

Destructive

Render the video. SPENDS THE USER'S CREDITS: ask first, with the direction, settings, cost and any watermark, and pass the cost as expected_credit_cost. External services render it; it gets a public share page and may send account email.

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>",
      "expected_credit_cost": "<expected_credit_cost>"
    },
    "name": "generate_video"
  }
}

Input Schema

Name	Required	Description	Default
`product_id`	Yes	The product to render. Its current direction and settings are used as-is.
`expected_credit_cost`	Yes	The cost you told the user, from get_product's video_direction.credit_cost. A stale one is refused, uncharged.

Output Schema

Name	Required	Description	Default
`queued`	Yes
`videos`	Yes
`next_step`	Yes
`product_id`	Yes
`workbench_url`	Yes
`credits_charged`	Yes
`opened_new_video`	Yes
`credits_remaining`	Yes
`email_on_completion`	No
`typical_wait_minutes`	Yes
`skipped_insufficient_credit`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Beyond the destructive/openWorld annotations it discloses the credit spend, the requirement to pass the agreed cost, that rendering happens on external services, that the result becomes a public share page, and that account email may be sent. These are exactly the side effects an agent needs before invoking a destructive tool.

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?

The most important fact — that it spends credits — is capitalized and front-loaded. The final clause about external services, share page and email is a compressed run-on, but no sentence is wasted.

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?

With an output schema present it need not describe return values, and the safety and cost profile is fully covered. The only gap is workflow context — whether a video direction must exist first and which sibling supplies the cost.

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 both parameters are already documented, including where expected_credit_cost comes from and that a stale value is refused uncharged. The description restates the cost-passing rule but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 opening 'Render the video' is a specific verb+resource, and the title adds that it spends credits. It implicitly separates this from read-side siblings like get_video or rate_video, but never names an alternative explicitly.

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?

It gives a clear precondition — confirm with the user first, showing direction, settings, cost and watermark — but gives no guidance on which sibling to call before or after (e.g. get_product to obtain the cost, get_video to check the result). Usage framing is implied rather than routed.

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.