Skip to main content
Glama

Outil.io

Inspect video asset

inspect_video_asset
Read-only

Durée réelle, présence de son, dimensions et URL d’un média du projet, vérifiées par FFprobe.

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": {
      "assetId": "<assetId>"
    },
    "name": "inspect_video_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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. The description adds one genuinely useful piece of behavior beyond that: values are verified by FFprobe, implying authoritatively probed rather than stored metadata. It says nothing about failure modes, e.g. what happens when the asset is an image or FFprobe fails, or about latency for large media.

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?

One compact sentence with no padding, and the returned properties are front-loaded before the FFprobe provenance. It loses a point only because the sentence is dense and written in French while the tool name, title and schema are English, creating a small comprehension seam for an agent operating in English.

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?

With no output schema, the description does the right thing by enumerating the four returned values, which is enough to know what comes back. However, for a probing tool it omits the asset-type precondition and any error/empty-result semantics, so an agent cannot tell how to react when the probe cannot produce those values.

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% and the single assetId parameter is never explained in the description. The schema only constrains it to a positive integer; the description does not say whether it is the project asset id, where to obtain it (list_video_assets is an obvious source but unmentioned), or how invalid ids behave.

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 concrete retrieval operation and enumerates the returned facts: real duration, audio presence, dimensions and media URL, for a project asset probed via FFprobe. That is much more specific than restating the name. It does not distinguish itself from nearby inspection siblings such as inspect_video_timeline or get_video_source_frame, which keeps it at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus the other inspect_* tools, no prerequisite (e.g. the asset must already be uploaded and be a video), and no exclusion. The agent must infer the calling context entirely from the name and sibling list.

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.