Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Analyze video

analyze_video
Read-only

Break any video ad into its transcript, on-screen text, beat list, duration, and frame timestamps. Study competitor ads and remix their structure.

Instructions

Break a video ad down into its structure: the verbatim transcript (voiceover + on-screen text) with a beat list, plus duration and sampled frame timestamps. Use to study a reference/competitor ad before remixing its structure. Costs ~a transcription call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesthe video URL (a served /generated/ path or a public http(s) video)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "durationSeconds": {
-      "description": "the video length in seconds",
-      "type": "number"
-    },
-    "frameTimes": {
-      "description": "timestamps (seconds) of the sampled frames",
-      "items": {
-        "type": "number"
-      },
-      "type": "array"
-    },
-    "transcript": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "verbatim voiceover + on-screen text with a beat list (null when silent/unreachable)"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds valuable context beyond that: the tool costs '~a transcription call' and extracts specific components such as voiceover vs on-screen text, beat lists, and frame timestamps. This gives the agent accurate expectations about cost and output.

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 sentences carry all essential information: output contents, intended use, and cost. The most important scoping information is front-loaded, with no filler or redundancy.

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

Completeness5/5

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

Despite having no output schema, the description clearly lists what the agent will receive (transcript, beat list, duration, timestamps), what input is needed (URL), and what tradeoff to expect (transcription cost). For a read-only analysis tool with a single parameter, this is complete.

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 100%, and the input schema already fully documents the url parameter. The description adds only light context that the URL should point to a video ad for structural analysis; it does not materially expand on the schema's parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Break down'), a specific resource ('a video ad'), and enumerates concrete outputs: verbatim transcript, beat list, duration, and sampled frame timestamps. This clearly distinguishes it from editing/generation siblings like edit_video, clip_video, and generate_video.

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?

The description gives an explicit use case: 'Use to study a reference/competitor ad before remixing its structure.' It provides clear workflow context for when to invoke the tool, though it does not explicitly name exclusion criteria or competing alternatives.

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