Skip to main content
Glama

Outil.io

Inspect video timeline

inspect_video_timeline
Read-only

Lire une portion de timeline : plans source et offsets, superpositions, audio et sous-titres actifs dans l’intervalle demandé.

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": "inspect_video_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
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 safety is covered. The description adds real value by naming what is visible in the interval (clips plus offsets, overlays, audio, subtitles), but does not disclose the hard 0–600 clause of the from/to window or what happens when the requested interval exceeds it.

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 front-loaded sentence with the resource first and the returned contents enumerated after the colon; nothing is wasted. It is slightly dense, packing four distinct returned entities into one clause, but well structured.

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 correctly spends its words on what comes back, which is the right call. However, for a three-parameter, read-only interval query it omits the units and bounds of the interval and never identifies the required projectId, leaving real gaps for invocation.

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 all parameter meaning, and it does not: neither from, to, nor projectId is named. Only 'intervalle demandé' hints at the time bounds, with no units (seconds vs frames), no defaults (0/600), and no indication that the upper limit is capped at 600.

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 ('Lire une portion de timeline') and enumerates the content returned: source shots and offsets, overlays, audio, active subtitles. This is clearly distinguishable from a project-level read, though it never contrasts itself with siblings such as inspect_video_asset or inspect_page_region.

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 only implied by the phrase 'dans l'intervalle demandé' — the agent can infer it is for reading a bounded time window of the timeline, but there is no explicit when-to-use, when-not-to-use, or alternative tool named. No mention of the required projectId precondition or of the 0–600 bound.

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.