Skip to main content
Glama

var2_get_video_result

Read-only

Status check for a VIDEO clip (not a song / voice-over / stitched render). "Is it ready / done yet?" / "check on it" / "where is my …" + placeholder_id or var2 link, media word = a VIDEO clip (not a song / voice-over / stitched render) → THIS tool. Status question with an id/link: NEVER answer null — one var2_get_*_result always matches; pick by MEDIA WORD. Action verbs ("animate it", "upscale", "extend it", "make a 3d model from it") → the matching create/modify tool with that url/id, NOT a status tool. Pair: var2_create_video. One immediate snapshot, never loop. NOT for routine progress checks: the inline preview in the chat updates itself when the job finishes — call this only when the user asks, or when you need the finished URL for a next step (then pass wait_seconds so ONE call waits for it - never check in a loop). Join/stitch renders → var2_check_join_status; voice-overs → var2_get_dialog_result. "Is this ready yet? www.var2.ai/video/" → THIS tool.

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": {
      "placeholder_id": "<placeholder_id>"
    },
    "name": "var2_get_video_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
wait_secondsNoOnly when you need the finished file URL for a next step: the call waits up to this many seconds and returns as soon as the asset is ready (images ~90, video / audio / 3D ~240). One waiting call - never check in a loop.
placeholder_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / wait_seconds
      Added value: +{
      +  "description": "Only when you need the finished file URL for a next step: the call waits up to this many seconds and returns as soon as the asset is ready (images ~90, video / audio / 3D ~240). One waiting call - never check in a loop.",
      +  "maximum": 240,
      +  "minimum": 0,
      +  "type": "number"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

readOnlyHint=true is already supplied, but the description adds behavior the annotations cannot convey: it is a single immediate snapshot, the chat's inline preview auto-updates so polling is unnecessary, and wait_seconds makes one call block until readiness. That is exactly the beyond-annotation context the bar asks for.

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?

Front-loaded with the core trigger and routed alternatives, with almost every clause carrying routing value. It loses a point for verbatim repetition — the '(not a song / voice-over / stitched render)' parenthetical and the 'never loop' warning each appear twice — and for telegraphic fragments that read awkwardly.

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?

No output schema exists, and the description covers the essentials: one snapshot, the finished URL use case, and the waiting behavior. It never says what a not-yet-ready response looks like (pending vs. failed state), which is the one gap for a status tool with no return schema.

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

Parameters4/5

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

Schema coverage is 50%: wait_seconds is well documented in-schema, while placeholder_id has no schema description. The description compensates by revealing that placeholder_id accepts either an id or a var2.ai/video/<id> link, and it reinforces the one-call wait semantics for wait_seconds, which the schema only partly covers.

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 ('Status check for a VIDEO clip') and immediately scopes it against the nearest confusions ('not a song / voice-over / stitched render'). The agent can distinguish it from var2_get_dialog_result, var2_get_audio_result and var2_check_join_status without opening any schema.

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?

Gives explicit use triggers ('Is it ready / done yet?', 'where is my …' + placeholder_id or var2 link), explicit exclusions (action verbs like 'animate it' or 'upscale' route to the create/modify tool), and names the concrete alternatives for the excluded media types. It even pre-empts the anti-pattern of looping and of answering null.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources