Skip to main content
Glama

analysis_get

Read-only

Fetch scene, beat, and face analysis for a video asset to select shots and align cuts to beat.

Instructions

Read analysis results: scenes (each shot with start/end, face coverage, face position and size — use it to pick shots), beats (tempo + beat times for beat-synced cuts), faces (same per-scene view).

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>",
      "kind": "<kind>"
    },
    "name": "analysis_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
assetIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint, so the description carries the disclosure burden, and it does so well by describing the returned payload shape for each kind (shot boundaries, face coverage, position and size, tempo and beat times). It omits error behavior and whether results must be pre-generated by analyze, but the core behavior of a read tool is conveyed.

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?

One dense sentence, front-loaded with the verb and resource, then structured by kind in parallel parentheses. No filler; every clause maps to a decision the caller has to make.

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 no output schema, the description correctly spends its words on return contents and covers all three kinds plus the intended use. It leaves open the assetId format and any dependency on a prior analyze run, which keeps it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must explain parameters, and it fully disambiguates the three kind enum values with the content each yields. assetId gets no explanation at all, which is the main remaining gap for a two-parameter tool.

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 definition opens with a specific verb and resource ("Read analysis results") and then enumerates the three result kinds with what each contains (scenes with start/end and face geometry, beats with tempo and times, faces as a per-scene view). It is clearly distinguishable from siblings like analyze or transcript_get in substance, though it never names an alternative explicitly.

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?

It offers actionable intent hints — "use it to pick shots" for scenes and "for beat-synced cuts" for beats — which tells the agent when the data is useful. It stops short of stating when not to call it, what to call first (e.g. analyze to produce results), or how it relates to siblings.

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