Skip to main content
Glama

Analyze a video

analyze_video
Read-onlyIdempotent

Show what Tuney sees in a video: picture cuts with their strength, where people speak, and a sonic-logo guess.

    Optional: score_video analyses the video by itself. Use this to discuss the edit with the user
    first, for example to pick the turning point or the moment the music should end.
    

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

Input Schema

NameRequiredDescriptionDefault
video_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive behavior, so safety is covered. The description adds one genuinely useful behavioral fact — this tool does not score the video itself, that is score_video's job — but says nothing about cost, latency, or whether the analysis is cached, which matters for an open-world analysis call.

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?

Two short sentences, front-loaded with what the tool returns before the alternative-tool guidance. Slightly muddled by the stray leading indentation/quotation residue and the vague word "Optional:" at the start of the second sentence, but nothing is padded.

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?

With an output schema present, the return values need not be spelled out, and annotations carry the safety profile; the description covers purpose, output shape at a high level, and the key relationship to score_video. The only real gap is how to obtain a valid video_id, which is what an agent most needs before calling.

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?

Schema description coverage is 0% for the single video_id parameter, and the description never mentions it, its provenance (e.g., from import_video or get_video_upload_link), or any format expectations. It compensates only indirectly because one parameter named video_id is largely self-explanatory, keeping this at the baseline rather than below it.

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 verb and resource ("Show what Tuney sees in a video") and enumerates the outputs — picture cuts with strength, speech regions, sonic-logo guess — which differentiates it from generic video tools. It is less crisp about what the deliverable actually is (an analysis result vs. a report), and the product-specific framing ("Tuney sees") adds slight ambiguity.

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 explicitly points at the sibling alternative ("score_video analyses the video by itself") and gives a concrete condition for choosing this tool ("to discuss the edit with the user first, for example to pick the turning point or the moment the music should end"). No negative exclusions are given, but the when-to-use context is clear.

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.