Skip to main content
Glama

media_ai

Analyze clips or bins with Studio AI tasks such as intelligent search, slate detection, audio classification, and deblurring to organize media and create new clips.

Instructions

Studio AI analysis on clips or a bin. task: 'intellisearch' (options: faces bool, better bool), 'slate' (options: marker_color), 'audio_classify', 'audio_classify_clear', 'deblur' (options: DeblurOptions dict, creates new clips).

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": {
      "task": "<task>"
    },
    "name": "media_ai"
  }
}

Input Schema

NameRequiredDescriptionDefault
binNo
taskYes
itemsNo
optionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important side effect — 'deblur' creates new clips. However, it says nothing about whether intellisearch/slate mutate marker/metadata state, whether analysis is long-running or GPU-bound, required permissions, or what the call returns.

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?

The description is front-loaded with the purpose and then dense with task/option detail; virtually no wasted words. The comma-and-quote layout is terse to the point of being slightly hard to parse, but it is efficient overall.

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

Completeness2/5

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

For a 4-parameter tool with zero annotation coverage, no output schema, and 0% schema descriptions, the entry omits too much: no explanation of bin vs. items, no return-value expectations, and side effects are documented for only one of five tasks.

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%, so the description must compensate. It partially does: 'task' is enumerated with five valid values, and per-task 'options' keys (faces, better, marker_color, DeblurOptions) are named. But 'bin' and 'items' are never explained and the interaction between them is unstated.

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 and resource ('Studio AI analysis on clips or a bin') and then enumerates the concrete task modes (intellisearch, slate, audio_classify, audio_classify_clear, deblur), so an agent knows what the tool does. It does not distinguish itself from the sibling clip_ai, which sounds closely related, keeping it below a 5.

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 only implied: the agent must infer that it should pick a 'task' and supply either 'bin' or 'items'. There is no explicit when-to-use, when-not-to-use, or comparison against clip_ai or the media_* siblings, and no prerequisites are stated.

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