Skip to main content
Glama
Sign In

Clypmint B-Roll

by com.clypmint
OverviewDiscussionsAdmin

Plan b-roll for a script

plan_broll
Read-only

Read a whole script, pick every moment that needs a cutaway (named things first, then concrete scenes), and find verified shots for each. Returns each moment with the exact words it starts on (and its time when word timings are given). For one subject use find_broll. Each moment is charged like a find_broll search, only when it finds verified shots.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "plan_broll"
  }
}

Input Schema

NameRequiredDescriptionDefault
wordsNoOptional word timings ({text, start, end} in seconds), so each moment comes back with its time.
rightsNo"licensed" (default): only media cleared for reuse. "any": also the open web, to get the real thing you name (a movie clip, a recent news photo, a screenshot of an event). Web results are marked license.cleared=false: the owner holds the rights, check before commercial use. Slower: about 7 s, at most 20 s.licensed
max_beatsNoThe most moments to find shots for.
transcriptNoThe script or transcript.
results_per_beatNoShots to return for each moment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the read-only/open-world/idempotency profile, and the description adds genuinely new facts: the per-moment billing model and, crucially, that charges apply "only when it finds verified shots." It doesn't mention the latency of the default licensed path (only the schema's rights param does) or any rate limits, so it stops short of full disclosure.

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?

Three sentences, front-loaded with the main action, and no filler. The middle sentence is a dense run-on bundling return shape with two parentheticals, which slightly hurts scanability but not substance.

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?

No output schema exists, and the description does sketch the return shape (per-moment, anchor words, optional time) plus cost. Missing only result ordering/limit interaction details (e.g., how max_beats and results_per_beat shape the response), a minor gap for a one-shot planning tool.

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 coverage is 100% and each parameter already carries a detailed description (including the rights trade-off and timing semantics), so the schema does the heavy lifting. The description adds only a small cross-reference — that moments come back time-stamped "when word timings are given" — which is baseline-3 territory.

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 chain (read script, pick moments, find verified shots) on a named resource, and explicitly draws the boundary against find_broll for the single-subject case. An agent can distinguish it from both siblings without reading any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"For one subject use find_broll" names the alternative and the condition that selects it. The prioritization rule ("named things first, then concrete scenes") also tells the agent what ordering to expect, which is usage-relevant behavior an agent cannot infer elsewhere.

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

All Clypmint B-Roll toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources