Clipform

Search Media

clipform_search_media

Read-onlyIdempotent

Search images or stock video clips. Pass one query or many (max 10) - multiple queries run in one call instead of separate tool calls. Use results to feed into clipform_generate_video for narrated slideshow videos, or upload directly as still images via clipform_upload_media_asset then clipform_attach_node_media. All results are pre-cleared for commercial use. Results include a description (alt text where the provider has it) - use it to pick visually distinct images.

Example: { queries: [{ query: "saturn rings" }, { query: "mars surface", count: 3 }] } returns portrait images for both.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`context`	Yes	Describe the user's underlying goal in one sentence - not the tool you're calling.
`queries`	Yes	One or more search queries to run

Output Schema

TableJSON Schema

Name	Required	Description	Default
`searches`	Yes	Results grouped by query (items empty if a query found nothing or failed)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 31, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Describe the user's underlying goal in one sentence - not the tool you're calling.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "queries"
-]New value: +[
+  "queries",
+  "context"
+]

Changed1 schema field changedJul 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "searches": {
+      "description": "Results grouped by query (items empty if a query found nothing or failed)",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "items": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "attribution": {
+                  "type": "string"
+                },
+                "duration": {
+                  "type": "number"
+                },
+                "height": {
+                  "type": "number"
+                },
+                "source": {
+                  "type": "string"
+                },
+                "title": {
+                  "type": "string"
+                },
+                "url": {
+                  "type": "string"
+                },
+                "width": {
+                  "type": "number"
+                }
+              },
+              "required": [
+                "url"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "kind": {
+            "enum": [
+              "image",
+              "video"
+            ],
+            "type": "string"
+          },
+          "query": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "query",
+          "kind",
+          "items"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "searches"
+  ],
+  "type": "object"
+}

First observedJul 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With readOnlyHint and idempotentHint already set, the description adds valuable behavior beyond annotations: batch execution in one call, all results pre-cleared for commercial use, and result descriptions/alt text. This gives the agent useful expectations without needing to infer them.

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

Conciseness5/5

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

Every sentence earns its place: scope, batching behavior, downstream workflows, licensing, result-description guidance, and a compact example. It is front-loaded with the main action and contains no filler.

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?

The description, together with the rich input schema and output schema, covers what the tool does, how to batch queries, what to do with results, and important constraints (commercial clearance, alt text). Nothing critical for a search tool is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds a concrete example showing the queries array shape, count override, and default portrait orientation. It also clarifies the semantic that multiple query objects run in one call, which the schema does not state.

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?

The description opens with a specific verb and resource ('Search images or stock video clips') and immediately differentiates from sibling tools by scope (media vs music/news). The downstream references to clipform_generate_video and clipform_upload_media_asset further anchor its role.

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?

It explicitly explains batching ('Pass one query or many (max 10) - multiple queries run in one call instead of separate tool calls') and the intended downstream paths for results. It does not explicitly name search_music/search_news as exclusions, but the scope statement makes the usage context clear.

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

All Clipform 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.