Skip to main content
Glama

Read what is known about a Playground clip

playground_video_analyze
Read-onlyIdempotent

Read-only facts about one video node: its clip URL, model and settings, frame nodes already taken from it, objective FFmpeg measurements (duration, black segments, silence, loudness) when the server has FFmpeg, and any visual analysis the Berrys agent already made of this exact clip. It never makes a new paid model call, so a new shot table or visual description is not produced here; ask the Berrys agent (playground_brief_start) for that.

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": {
      "projectId": "<projectId>",
      "videoNodeId": "<videoNodeId>"
    },
    "name": "playground_video_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
videoNodeIdYesExisting canvas video node ID containing the source video.

Output Schema

NameRequiredDescriptionDefault
framesYes
metadataYes
revisionYes
canvasUrlYes
videoNodeIdYes
measurementsYes
priorAnalysisYes
perceptualAnalysisYes
measurementsUnavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the bar is lower, yet the description adds real context: no paid model call is made, and FFmpeg measurements are only present "when the server has FFmpeg", which explains partial results an agent might otherwise misread as failure. It could go further on how missing analysis should be handled, but the cost and conditional-capability disclosures are genuinely useful.

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 returned content is front-loaded in the first sentence and the exclusion/routing rule follows immediately after. The first sentence is long and list-heavy, but every enumerated item is substantive rather than filler, so only minor tightening is possible.

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?

For a two-parameter read tool with full annotation coverage, a complete schema and an output schema, the description supplies the remaining decision-relevant context: what is included, the conditional FFmpeg dependency, the cached-analysis caveat, and the correct route when fresh analysis is needed. Nothing an agent requires to select and call it correctly is missing.

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 both required parameters (projectId, videoNodeId) are fully documented in the schema, so the baseline of 3 applies. The description reinforces that the node must be an existing clip and that analysis is tied to "this exact clip", but adds no format or lookup guidance beyond the schema text.

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?

States a specific verb and resource ("read-only facts about one video node") and then enumerates exactly what is returned: clip URL, model and settings, frame nodes, FFmpeg measurements, and prior visual analysis. It also explicitly marks the boundary against playground_brief_start, so an agent can separate it from the neighbouring tools without opening either schema.

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?

Gives an explicit when-not-to-use rule and names the alternative: it "never makes a new paid model call", so a new shot table or visual description must come from playground_brief_start. The positive trigger (inspect what already exists before spending) is implied rather than spelled out, which keeps it just below a 5.

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.