Skip to main content
Glama

Clipform

by io.github.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
NameRequiredDescriptionDefault
tagsNoGenre/mood tags to filter by
countNoMax results (default: 5)
queryYesWhat to search for (e.g. 'upbeat quiz background', 'calm ambient', 'playful pizzicato')
contextYesDescribe the user's underlying goal in one sentence - not the tool you're calling.
maxDurationNoMaximum duration in seconds
minDurationNoMinimum duration in seconds
instrumentalOnlyNoOnly instrumental tracks (default: true)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
tracksYesMatching tracks (empty if none); pass a url as the audio track to generate_video

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds meaningful behavioral context: the tool returns royalty-free audio assets with licensing info, and the results are intended to be passed into video generation. This goes beyond the structured annotations.

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 compact, front-loaded with the core purpose, and every sentence adds value: scope, use cases, integration targets, and return contents. No filler or redundant restatement.

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 search tool with rich annotations and a complete output schema, the description covers the key contextual needs: what kind of audio is returned, license status, recommended use cases, and how to consume the returned URL. Nothing essential 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%, so the schema fully documents parameters like tags, count, duration filters, and instrumentalOnly. The description does not add parameter-level detail, but that is acceptable given the schema already carries the burden.

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 clear, specific action ('Search for royalty-free music tracks and ambient sounds') and differentiates the tool from sibling search tools (search_media, search_news). It also clarifies the expected result type by listing download URLs, duration, artist, and license info.

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-case guidance: quiz forms, multi-step surveys, and longer forms. It also explains downstream usage by naming clipform_generate_video and clipform_render_video_template. It does not explicitly mention when not to use it or name search_media as the alternative, so it stops 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 Clipform toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation3/5

Most form/node CRUD tools are clearly distinct, but the render/generate trio (generate_video, render_video_template, render_composition) and get_responses vs get_results can be confused by name alone. The descriptions include strong disambiguation guidance, so the overlap is manageable but still present.

Naming Consistency4/5

The vast majority of tools follow a consistent clipform_verb_noun snake_case pattern, with create/get/update/delete/list used predictably. Minor deviations include get_more_tools lacking the clipform_ prefix and whoami not matching the verb_noun convention.

Tool Count2/5

At 34 tools, this is above the range where a toolset feels well-scoped, and several entries are auxiliary or internal (whoami, log_generation, get_more_tools, search_news). The domain is broad, but the surface could be consolidated without losing core capabilities.

Completeness4/5

The set covers form and node lifecycle, media upload/attachment, logic wiring, publishing, responses/results, and content generation (TTS, video, music, stock media). Minor gaps remain, such as no conditional branching in set_logic and no general media-library listing tool.

Resources