Skip to main content
Glama

Answer a question about a video

analyze_video

Answers natural-language questions about a full video or time range, returning approximate timestamps. Check video_info first for limits; local files upload to Google and use API quota.

Instructions

Answer a question about a whole video or a time range, with approximate timestamps. Local files are uploaded to Google for processing; this call is billed to the user's API quota. Use video_info first to check limits.

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": {
      "source": "<source>",
      "question": "<question>"
    },
    "name": "analyze_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNonormal
sourceYes
refreshNo
questionYes
end_secondsNo
start_secondsNo

Output Schema

NameRequiredDescriptionDefault
cacheNo
modelYes
usageNo
answerYes
detailYes
segmentNo
warningsNo
confidenceNomedium
key_pointsNo
timestampsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well by disclosing that local files are uploaded to Google, that processing consumes the user's billed API quota, and that timestamps are approximate. It does not further explain processing constraints, caching behavior, or failure behavior.

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 compact sentences front-load the purpose and then cover privacy, cost, and the prerequisite check. Each sentence adds useful operational information without redundancy.

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?

The output schema removes the need to document return fields, and the description covers the main selection, privacy, billing, and sequencing concerns. However, for a six-parameter tool with no annotations or schema descriptions, missing source requirements and unexplained optional parameters prevent it from being fully sufficient for reliable 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?

At 0% schema description coverage, the description only implies that source may be a local file and that start_seconds and end_seconds define the optional time range. It gives no accepted source syntax or supported source types and does not explain the detail or refresh parameters, leaving important invocation semantics undocumented.

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 clearly states the verb and resource: answering a question about a whole video or a selected time range, with approximate timestamps. It does not explicitly distinguish this question-answering operation from siblings such as find_moments or extract_frames.

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?

It supplies clear scope through 'whole video or a time range' and gives a concrete prerequisite: 'Use video_info first to check limits.' It lacks when-not guidance or explicit routing to other video tools for different tasks.

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

Deploy Server

Other Tools