Instavar Video Templates and Studio

Prepare a copy edit for approval

edit_video_brief

Read-onlyIdempotent

Prepare exact title, script or caption changes for an existing private video. Returns a Studio approval link; this call does not save copy or start a render. The signed-in user must review and approve there. Approval changes the current run, consumes rerender credits and revokes existing review links. Previous run records are retained. Does not publish. Preserve requestId for unchanged retries.

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": {
      "jobId": "<jobId>",
      "requestId": "<requestId>",
      "confirmed": "<confirmed>"
    },
    "name": "edit_video_brief"
  }
}

Input Schema

Name	Required	Description
`jobId`	Yes	The existing video's job ID, from list_video_projects or create_video_brief.
`title`	No	New title, if it changes.
`script`	No	New spoken words, if they change.
`caption`	No	New social caption, if it changes.
`confirmed`	Yes	Set only after the user asks for these exact copy changes.
`requestId`	Yes	Stable retry identity for this exact proposal. Reuse after uncertain responses.
`workspaceId`	No	Optional workspace override. For a new plan, omit this field so the server resolves the account default. A workspace ID returned by an account read is not a user selection. Supply this field only for a user-selected workspace or the workspace of an existing saved project. Ask only when the server requires selection; never fall back after denied access.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 29, 2026

addedInput schema / properties / caption / description
```
Added value: +"New social caption, if it changes."
```

addedInput schema / properties / confirmed / description

Added value: +"Set only after the user asks for these exact copy changes."

addedInput schema / properties / jobId / description

Added value: +"The existing video's job ID, from list_video_projects or create_video_brief."

addedInput schema / properties / requestId / description

Added value: +"Stable retry identity for this exact proposal. Reuse after uncertain responses."

addedInput schema / properties / script / description
```
Added value: +"New spoken words, if they change."
```
addedInput schema / properties / title / description
```
Added value: +"New title, if it changes."
```

First observedOct 26, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: returns a Studio approval link, requires human approval, approval consumes rerender credits, revokes existing review links, retains prior run records, and warns to preserve requestId for unchanged retries. Crucially it reconciles with readOnlyHint=true by stating this call itself performs no mutation — the side effects occur at the separate approval step — so the safety profile is not contradicted.

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?

Five short sentences, front-loaded with what the tool does, then what it does not do, then the consequences of the follow-up approval. No filler and no repetition of the title or name.

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?

There is no output schema, and the description compensates by explaining exactly what comes back (a Studio approval link) and that nothing is persisted yet. For a seven-parameter, three-required staging tool with full schema coverage, nothing an agent needs to call it correctly is missing.

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%, so jobId, title, script, caption, confirmed, requestId and workspaceId are already documented in detail. The description echoes the editable fields ('title, script or caption changes') and adds a retry hint for requestId, but that hint largely restates the schema's own 'Reuse after uncertain responses'. Baseline 3 applies when the schema carries the load.

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 and resource ('Prepare exact title, script or caption changes for an existing private video') and immediately scopes it against the sibling create_video_brief by requiring an existing private video. The agent knows this stages a proposal rather than creating or publishing anything.

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?

Explicitly names the boundary conditions: 'this call does not save copy or start a render' and 'Does not publish', plus the required follow-up that 'The signed-in user must review and approve there.' It stops short of naming a sibling alternative (e.g. review_video_project or propose_video_storyboard) or stating the precondition that the video be private, so the routing is clear but not fully exhaustive.

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

All Instavar Video Templates and Studio 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.