Clypmint

Find b-roll

find_broll

DestructiveIdempotent

Real media and licensed stock, vision-checked; import_media brings one in. $0.02 a search. Cost: Costs $0.02 a search ($0.06 with web), from the b-roll balance, only when verified shots come back.

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": {
      "query": "<query>"
    },
    "name": "find_broll"
  }
}

Input Schema

Name	Required	Description
`web`	No	Adds the open web (not cleared).
`line`	No	The line it plays over.
`type`	No	Pictures or clips.
`query`	Yes	What to show.
`orientation`	No	The video's shape.

Output Schema

Name	Required	Description	Default
`code`	No
`cost`	No
`error`	No
`state`	No
`status`	No
`dry_run`	No
`message`	No
`plan_id`	No
`style_id`	No
`video_id`	No
`available`	No
`import_id`	No
`output_id`	No
`studio_url`	No
`version_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 10, 2026

addedInput schema / properties / line

Added value: +{
+  "description": "The line it plays over.",
+  "maxLength": 1000,
+  "type": "string"
+}

addedInput schema / properties / orientation

Added value: +{
+  "description": "The video's shape.",
+  "enum": [
+    "landscape",
+    "portrait",
+    "square",
+    "any"
+  ],
+  "type": "string"
+}

changedInput schema / properties / query / description

Previous value: -"What to show, in plain words."New value: +"What to show."

addedInput schema / properties / type

Added value: +{
+  "description": "Pictures or clips.",
+  "enum": [
+    "image",
+    "video",
+    "any"
+  ],
+  "type": "string"
+}

changedInput schema / properties / web / description

Previous value: -"true adds the open web (not cleared, costs more)."New value: +"Adds the open web (not cleared)."

AddedNov 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the annotations, it discloses real behavioral facts: a per-search charge drawn from a "b-roll balance," a higher rate when the web is enabled, and the key conditional that the charge applies only "when verified shots come back." It also flags that web results are "not cleared," a licensing caveat an agent cannot get from the schema. It doesn't explain why destructiveHint=true applies (presumably balance spend) or any rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is front-loaded and efficient, but the cost is stated twice — "$0.02 a search" followed by "Cost: Costs $0.02 a search ($0.06 with web)" — which is redundant and reads as stitched-together fragments. The meaning survives, but a sentence is not earning its place.

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 an output schema present, return shape needn't be explained, and all five parameters are documented. The description covers purpose, cost model, billing conditional, licensing caveat, and the handoff to import_media. It leaves minor gaps around what the b-roll balance is and whether repeated identical searches bill again.

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 includes enum values and descriptions for both enum'd parameters, so the schema already carries parameter meaning. The description's only added parameter context is the differential cost tied to the web flag ($0.02 vs $0.06). That is useful but thin, so the baseline 3 applies.

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?

"Real media and licensed stock, vision-checked" states the resource and its quality bar, and the title supplies the verb "Find." It also carves out the boundary against import_media ("import_media brings one in"), so an agent can tell search from ingestion. It stops short of saying "search b-roll clips and images" in one explicit verb+resource phrase, which is why it's not 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 Guidelines4/5

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

The description routes the agent through a clear workflow: use this to find, then hand off to import_media to bring the asset in. Pricing context ("$0.02 a search") implicitly signals this is a metered step to use deliberately rather than speculatively. No explicit when-not conditions are given, so it falls short of a 5.

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

All Clypmint tools Inspect

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

Need Help?