Skip to main content
Glama

Outil.io

List video exports

list_video_exports
Read-only

Lire les dix derniers exports d’un montage, notamment après une déconnexion ou un timeout.

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": {
      "projectId": "<projectId>"
    },
    "name": "list_video_exports"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds real behavioral context beyond that: it is capped at the ten most recent exports, and it is the appropriate call after a lost connection. It does not describe ordering beyond 'derniers', nor whether an empty result means none exist versus none pending.

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?

A single short sentence with the scope constraint front-loaded and the recovery scenario trailing. No filler, but it is thin enough that a little more structure (e.g. an explicit 'for a given project') would cost nothing and add clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, read-only list tool with annotations covering the safety profile and no output schema, the essentials are present: scope of results and typical trigger. It is still incomplete on result shape (what fields an export carries) and on whether the ten-item cap is fixed or truncated, which an agent needs to interpret an empty or short list.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the parameter meaning, and it only partly does. The phrase 'd'un montage' clarifies that the required projectId refers to a video montage/edit, but it never mentions the parameter name, that it is a UUID, or that it is mandatory. An agent still has to read the schema to know what to pass.

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 and resource: read the last ten exports of a montage/edit. That is clearly distinguishable from siblings like list_video_assets or list_video_projects. It loses a point because the description is in French while the name, title and sibling names are in English, and it never uses the word 'video' to tie the resource back to the tool name.

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?

Gives an implied usage context: notably after a disconnection or timeout, i.e. as a recovery/verification call. It does not say when to prefer another tool, nor whether this is the only way to enumerate exports, so the guidance is suggestive rather than directive.

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.