Skip to main content
Glama

VideoGen

by io.github.dg314
OverviewDiscussionsAdmin

Get tool execution

get_tool_execution
Read-onlyIdempotent

Return a tool execution snapshot with status, progress, attemptIndex, error details, and results. Each result includes fileId, file metadata, downloadUrl, and thumbnailUrl when available. Use this to poll a started generation without creating another asset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolExecutionIdYesExecution to inspect or cancel. Use toolExecutionId from a media-tool start result or list_tool_executions.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorYesError details when status is failed; otherwise null.
statusYesJob status: pending, running, succeeded, failed, or cancelled.
resultsYesGenerated results; empty until succeeded.
toolTypeYesTool name (e.g. GENERATE_IMAGE).
attemptIndexYesCurrent or latest attempt index.
toolExecutionIdYesTool execution id (vg_tool_...).
progressPercentageYesCompletion progress 0-100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / toolExecutionId / description
      Previous value: -"Tool execution id (vg_tool_...)."New value: +"Execution to inspect or cancel. Use toolExecutionId from a media-tool start result or list_tool_executions."
    • changedOutput schema / description
      Previous value: -"Tool execution id, or full execution status after waiting (results when succeeded)."New value: +"Full tool-execution status snapshot."
    • changedOutput schema / properties / progressPercentage / description
      Previous value: -"Completion progress 0-100 (present after polling)."New value: +"Completion progress 0-100."
    • changedOutput schema / properties / results / description
      Previous value: -"Generated results with download URLs when succeeded."New value: +"Generated results; empty until succeeded."
    • changedOutput schema / required
      Previous value: -[
-  "toolExecutionId"
-]New value: +[
+  "toolExecutionId",
+  "status",
+  "toolType",
+  "progressPercentage",
+  "attemptIndex",
+  "results",
+  "error"
+]
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds that this is a polling operation and that thumbnailUrl is present only "when available", which is real value, but it says nothing about polling cadence, terminal statuses, or how error details/attemptIndex behave across retries.

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?

Three short sentences, front-loaded with the return payload and then the usage condition. No filler, no repetition of the tool name or title.

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 annotations covering the safety profile and an output schema present, the description does not need to enumerate return values, yet it briefly does anyway. The remaining gap is operational: no guidance on how often to poll or what status values indicate completion.

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 single parameter already explains where to source toolExecutionId (start result or list_tool_executions). The description adds no parameter-level detail, so the baseline of 3 for fully documented schemas 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?

States a specific verb (Return) and resource (tool execution snapshot) plus the fields it carries (status, progress, attemptIndex, error details, results), so the agent knows exactly what it gets. It does not name list_tool_executions or cancel_tool_execution, the nearest siblings, so differentiation is implied rather than explicit.

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?

"Use this to poll a started generation without creating another asset" gives a clear when-to-use condition and implicitly steers away from re-invoking a generation tool. It stops short of naming the alternatives (list_tool_executions, cancel_tool_execution) or stating exclusions, so it is context rather than full routing guidance.

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

All VideoGen toolsInspect
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.

Resources