Skip to main content
Glama

Outil.io

Get video export

get_video_export
Read-only

Lire l’état queued/rendering/done/failed d’un export. done fournit le fichier MP4 et sa version ; ne pas annoncer un succès avant cet état.

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": {
      "exportId": "<exportId>"
    },
    "name": "get_video_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
exportIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds genuinely new behavior: the full state machine, the fact that 'done' yields the MP4 file and its version, and the warning not to report success before that state. It does not cover polling cadence or whether failed states are terminal, so it is not exhaustive.

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?

Two short sentences with the state list front-loaded and the usage caution second; every clause carries information and nothing is redundant.

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?

There is no output schema, so the description must convey return semantics — it does explain what 'done' returns (MP4 file plus version) and that the other states carry no file. It leaves the payload of queued/rendering/failed unspecified, which is a minor gap for a single-parameter status tool.

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?

Only one parameter exists (exportId, uuid) and the schema gives it no description, so the description carries the burden — yet it never explains where exportId comes from or what format it takes. The parameter name plus format:uuid is largely self-evident, so this is a moderate rather than severe gap.

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 description states a specific verb and resource ('Lire l'état ... d'un export') and enumerates the exact state values (queued/rendering/done/failed), which clearly separates it from siblings like start_video_export or list_video_exports. It does not explicitly name an alternative tool, but the operation itself is unambiguous.

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?

Usage is implied rather than stated: the tool reads status, so it is a polling companion to start_video_export. The clause 'ne pas annoncer un succès avant cet état' is a useful behavioral rule about when a result may be treated as final, but there is no explicit when-to-use/when-not-to-use guidance or named alternative.

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.