Clipform

Search Music

clipform_search_music

Read-onlyIdempotent

Search for royalty-free music tracks and ambient sounds. Quiz forms especially benefit from background music - it keeps energy up between questions. Also consider it for multi-step surveys and longer forms. Pass the returned URL as the audio track to clipform_generate_video, or as the audio for the slideshow video template via clipform_render_video_template. Returns download URLs, duration, artist, and license info.

Input Schema

TableJSON Schema

Name	Required	Description
`tags`	No	Genre/mood tags to filter by
`count`	No	Max results (default: 5)
`query`	Yes	What to search for (e.g. 'upbeat quiz background', 'calm ambient', 'playful pizzicato')
`context`	Yes	Describe the user's underlying goal in one sentence - not the tool you're calling.
`maxDuration`	No	Maximum duration in seconds
`minDuration`	No	Minimum duration in seconds
`instrumentalOnly`	No	Only instrumental tracks (default: true)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`tracks`	Yes	Matching tracks (empty if none); pass a url as the audio track to generate_video

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: -[
-  "query"
-]New value: +[
+  "query",
+  "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": {
+    "query": {
+      "type": "string"
+    },
+    "tracks": {
+      "description": "Matching tracks (empty if none); pass a url as the audio track to generate_video",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "artist": {
+            "type": "string"
+          },
+          "duration": {
+            "type": "number"
+          },
+          "license": {
+            "type": "string"
+          },
+          "source": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "tracks"
+  ],
+  "type": "object"
+}

First observedJul 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds behavioral context by noting the results are royalty-free download URLs and that they can be passed into video generation/render tools. This goes beyond the annotations without contradicting 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?

The description is well-structured: purpose first, usage context second, integration guidance third, and returned fields last. Every sentence earns its place, and the length is appropriate for the tool's complexity. It is informative without being verbose.

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 tool has an output schema, detailed parameter descriptions, and clear annotations, so the description does not need to repeat those details. It adds the missing integration context by explaining how to pass the returned URL to video tools. For an agent selecting and invoking this tool, the description is complete.

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%, so the schema already documents every parameter. The description does not add meaningful parameter-level guidance beyond mentioning that the returned URL can be used as audio, which relates to output rather than a specific parameter. Baseline 3 is appropriate here.

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 states a specific verb and resource: 'Search for royalty-free music tracks and ambient sounds.' This clearly distinguishes it from sibling tools like clipform_search_media and clipform_search_news by tool type and content category. It also outlines downstream usage, reinforcing what the tool produces.

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 gives concrete use cases: 'Quiz forms especially benefit from background music' and 'Also consider it for multi-step surveys and longer forms.' It explains why music fits these contexts. It does not explicitly state when not to use it or name alternatives, but the guidance is clear enough for a niche search tool.

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.