Skip to main content
Glama

Search clips

search_clips

Search a multilingual catalog of verified short video clips by query, duration, aspect ratio, orientation, language, or source; optionally queue imports for missing clips.

Instructions

Search verified clips; optionally queue an import.

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": "search_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNo
limitNo
queryYes
cursorNo
sourceNo
languageNo
has_audioNo
min_widthNo
aspect_ratioNo
max_durationNo
import_if_missingNo

Output Schema

NameRequiredDescriptionDefault
clipsYes
statusNo
request_idNo
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and openWorldHint=true; the phrase "optionally queue an import" is consistent with that and usefully signals the side effect. However, it never says what triggers the import, that it is asynchronous, or what permissions/rate limits apply, so the disclosure stops short of real behavioral context.

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?

Two short clauses, front-loaded and free of padding, but the brevity is under-specification rather than economy given an 11-parameter tool. The semicolon structure is clean but the second clause is ambiguous about conditionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be described, but with 11 parameters at 0% coverage and a mutation side effect, the description is far too thin. It should at minimum explain the import trigger and the key filtering parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Eleven parameters with 0% schema description coverage, and the description explains none of them. Only a faint hint at import_if_missing via "queue an import"; query, source, cursor, fps, aspect_ratio, max_duration and the rest carry no meaning beyond their names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Search verified clips" gives a verb and resource, but "verified" is undefined and the second clause ("optionally queue an import") muddies whether this is a read or a write tool. It does not distinguish itself from the sibling search_and_import, which an agent would need to choose between.

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

Usage Guidelines2/5

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

No when-to-use guidance, no when-not-to-use, and no mention of the obvious alternative search_and_import. The agent is left to infer from the name alone whether to call this or the sibling.

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