Skip to main content
Glama
Sign In

cliphou.se release videos

by se.cliphou
OverviewDiscussionsAdmin

Search video templates

search_templates
Read-only

Find marketing video templates for a product, project, or announcement. Prefer a marketing goal and, when project facts support it, a release moment; then add a short product or style query. Returns a searchId, the selected moment, detectedMoments hints, and results with id, title, goals, moments, aspect, length, preview MP4, poster image, and editor URL. Engine details appear only when the engine filter is used.

Input Schema

NameRequiredDescriptionDefault
goalNoMarketing goal. One of: launch-product (Launch a product), announce-feature (Announce a feature), share-update (Share an update), grow-waitlist (Grow a waitlist), announce-integration (Announce an integration), announce-pricing (Announce pricing), celebrate-milestone (Celebrate a milestone), share-social-proof (Share social proof), promote-event (Promote an event), introduce-brand (Introduce a brand), run-promotion (Run a promotion), hire-team (Hire for the team).
limitNoMaximum results, default 6.
musicNotrue for beat-synced templates with a generated soundtrack, false for silent ones.
queryNoShort product or style description, for example "developer tool" or "minimal logo".
aspectNoOnly when the destination implies it: 9:16 vertical (Reels, TikTok, Shorts), 16:9 (YouTube, web), 1:1 or 4:5 (feeds).
engineNoAdvanced source-package filter. Omit unless the user explicitly asks for an engine.
momentNoRelease moment backed by project facts. Filters and ranks templates for it. One of: most-requested-feature (Most-requested feature shipped), generally-available (Available to everyone), limit-raised (A limit was raised or removed), faster (Something got faster), manual-step-removed (A manual step disappeared), integration-live (An integration went live), pricing-changed (Pricing changed), reliability-fix (A reliability fix landed), new-language-or-region (New language or region), new-platform (New platform), free-resource (Free tool or resource released), milestone (A real milestone was reached).
purposeNoExact catalog purpose, for example "Product launch".
maxSecondsNoMaximum video length in seconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / moment
      Added value: +{
+  "description": "Release moment backed by project facts. Filters and ranks templates for it. One of: most-requested-feature (Most-requested feature shipped), generally-available (Available to everyone), limit-raised (A limit was raised or removed), faster (Something got faster), manual-step-removed (A manual step disappeared), integration-live (An integration went live), pricing-changed (Pricing changed), reliability-fix (A reliability fix landed), new-language-or-region (New language or region), new-platform (New platform), free-resource (Free tool or resource released), milestone (A real milestone was reached).",
+  "enum": [
+    "most-requested-feature",
+    "generally-available",
+    "limit-raised",
+    "faster",
+    "manual-step-removed",
+    "integration-live",
+    "pricing-changed",
+    "reliability-fix",
+    "new-language-or-region",
+    "new-platform",
+    "free-resource",
+    "milestone"
+  ],
+  "type": "string"
+}
  2. Changed3 schema fields changed
    • changedInput schema / properties / engine / description
      Previous value: -"Rendering engine of the source package. Usually omit."New value: +"Advanced source-package filter. Omit unless the user explicitly asks for an engine."
    • addedInput schema / properties / goal
      Added value: +{
+  "description": "Marketing goal. One of: launch-product (Launch a product), announce-feature (Announce a feature), share-update (Share an update), grow-waitlist (Grow a waitlist), announce-integration (Announce an integration), announce-pricing (Announce pricing), celebrate-milestone (Celebrate a milestone), share-social-proof (Share social proof), promote-event (Promote an event), introduce-brand (Introduce a brand), run-promotion (Run a promotion), hire-team (Hire for the team).",
+  "enum": [
+    "launch-product",
+    "announce-feature",
+    "share-update",
+    "grow-waitlist",
+    "announce-integration",
+    "announce-pricing",
+    "celebrate-milestone",
+    "share-social-proof",
+    "promote-event",
+    "introduce-brand",
+    "run-promotion",
+    "hire-team"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Short description of the video, for example \"saas product launch\" or \"logo intro\"."New value: +"Short product or style description, for example \"developer tool\" or \"minimal logo\"."
  3. Changed7 schema fields changed
    • addedInput schema / properties / aspect
      Added value: +{
+  "description": "Only when the destination implies it: 9:16 vertical (Reels, TikTok, Shorts), 16:9 (YouTube, web), 1:1 or 4:5 (feeds).",
+  "enum": [
+    "16:9",
+    "9:16",
+    "4:5",
+    "1:1"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / engine / description
      Added value: +"Rendering engine of the source package. Usually omit."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum results, default 6."
    • addedInput schema / properties / maxSeconds
      Added value: +{
+  "description": "Maximum video length in seconds.",
+  "maximum": 600,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / music
      Added value: +{
+  "description": "true for beat-synced templates with a generated soundtrack, false for silent ones.",
+  "type": "boolean"
+}
    • addedInput schema / properties / purpose / description
      Added value: +"Exact catalog purpose, for example \"Product launch\"."
    • addedInput schema / properties / query / description
      Added value: +"Short description of the video, for example \"saas product launch\" or \"logo intro\"."
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds value beyond that by enumerating what is returned (searchId, selected moment, detectedMoments hints, result fields) and noting that "Engine details appear only when the engine filter is used" — a genuine behavioral detail. No output schema exists, so this return disclosure is meaningful.

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

Conciseness4/5

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

Three sentences, front-loaded with the core purpose. The middle sentence packs the recommended invocation order and the third lists return fields. Efficient overall, though the returns sentence is long and slightly dense.

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 no output schema, the description carries the return-value burden and does so adequately. Annotations cover safety, and the description covers purpose, query construction, and outputs. A 9-parameter optional tool could say a bit more about edge cases or empty-result behavior, but nothing essential 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. The description goes further by prescribing a priority order (goal first, moment when supported by facts, then query), which adds invocation guidance beyond the per-field schema text. It does not document field formats the schema lacks, so it earns a modest bump.

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?

States a specific verb and resource: "Find marketing video templates" for a product/project/announcement. Clear enough that an agent knows this is a template search operation. It does not explicitly distinguish itself from siblings like get_template_spec, so it stops just short of 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 Guidelines3/5

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

"Prefer a marketing goal and, when project facts support it, a release moment; then add a short product or style query" gives sequencing guidance for building a query. However, it never states when to use this tool versus siblings such as get_template_spec or render_preview, so usage context is only implied.

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

All cliphou.se release videos toolsInspect
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