Skip to main content
Glama

analyze_media

Runs AI analysis on clips or bins for transcription with speaker detection, audio classification, face indexing, slate detection, or motion-blur removal in DaVinci Resolve Studio.

Instructions

AI analysis on a clip ("clip:...") or a whole bin ("folder:..."): transcription (with speaker detection, optionally of nested clips), audio classification, IntelliSearch indexing (faces), slate detection (marks with a MARKER_* color) or motion-blur removal (see get_api_type('DeblurOptions')). Some need Resolve Studio and downloaded AI extras.

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": {
      "target": "<target>",
      "action": "<action>"
    },
    "name": "analyze_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
nestedNo
targetYes
better_qualityNo
deblur_optionsNo
identify_facesNo
speaker_detectionNo
slate_marker_colorNoMARKER_BLUE

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations only carry the generic readOnly=false / destructive=false / openWorld=false profile, so the description adds real value by disclosing the Resolve Studio and AI-extras prerequisites and the nested/speaker-detection options. It says nothing about runtime cost, failure behavior, or whether results are written into clip metadata, and it does not flag that the clear_* actions remove existing data despite destructiveHint=false.

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 sentences, front-loaded with the core verb and target syntax, and each parenthetical adds a real constraint rather than filler. The heavy parenthetical nesting makes it dense to parse, but nothing is redundant.

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?

For an 8-parameter, no-output-schema tool with 0% schema coverage and thin annotations, the description covers most parameters plus prerequisites, which is respectable. Gaps remain: better_quality is unexplained and there is no hint about what the call returns or where results land, which matters for an analysis tool.

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?

With 0% schema description coverage the description must compensate, and it largely does: target prefix syntax, nested, speaker_detection, identify_faces (IntelliSearch faces), slate_marker_color (MARKER_* colors), and deblur_options (pointed at get_api_type('DeblurOptions')) are all explained. Only better_quality is left completely unaddressed.

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+resource ('AI analysis on a clip or whole bin') and then enumerates the concrete operations (transcription, audio classification, IntelliSearch indexing, slate detection, motion-blur removal) that map onto the action enum. The 'clip:...' vs 'folder:...' target prefixes further sharpen scope, though it never names a sibling tool it replaces.

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 implied through the target-prefix convention and the action list, and one prerequisite is given ('Some need Resolve Studio and downloaded AI extras'). However there is no explicit when-to-use/when-not guidance, no mention that clear_* actions are the inverse of their analyze counterparts, and no routing to alternatives like get_api_type beyond the DeblurOptions pointer.

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